[mythtv] Scheduler needs table keys?

[Bruce Markey]

Chris Pinkham wrote:
...
> Personally, I think that if there isn't a locking issue then it doesn't
> matter if it takes 10-20 seconds to run at low priority.  I do think
> we need to do something about it running repetitively like when you're
> going through Watch Recordings and cleaning up stuff.  It would be nice
> if the first signal triggered an immediate resched.  If another signal
> was received within X seconds of the first resched finishing, then we'd
> wait for a few seconds before doing another resched.  Perhaps this would
> only be done on rescheds triggered by deletes.

Requests are already queued while the scheduler is running and
it is optimized so that it throws out recid 0 if there are any
recid > 0 and a recid -1 (full matching) will blow off every-
thing else in the queue and cut to the chase.

--  bjm