[mythtv] [ivtv-devel] trunk driver

[Chris Pinkham]

* On Wed Jan 24, 2007 at 03:39:57PM +0100, Attila Nagy wrote:
> > I can see the recordedmarkup changes being a part of the problem,
> > but I think the bigger issue is the locking of the recorded table
> > by the scheduler which blocks the recorder's main processing loop
> > because it is trying to update the filesize in the recorded table.
> 
> What if you try to transform your tables (or at least the recorded
> table) into InnoDB type tables? Those tables support transactions, so
> a long select does not block the updates on the table. As I've seen
> the scheduler does not lock the tables implicitly, so it is the MyISAM
> engine, that blocks the update.

Can't comment too much on that, but I think I remember there being
reasons that we hadn't done this already.  This would only be a band-aid
anyway.  The SQL updates for the filesize and seektable should not be
allowed to block the actual recording thread.  The recording is the most
important thing, we can get the filesize and rebuild the seektable later
if necessary.

--
Chris