[mythtv-users] RecordedSeek Table Size
Michael T. Dean
mtdean at thirdcontact.com
Tue Jul 24 17:59:32 UTC 2007
On 07/24/2007 01:13 PM, Nick Morrott wrote:
> On 24/07/07, Chris Tepe <cstepe at ctdataservices.com> wrote:
>
>> I recently had an issue with the database where I had to repair the
>> recordedseek table. My table is >40 megs and has more than a million
>> records in it. Is this normal and should I be concerned. I'm running
>> myth .20 on FC4.
>>
>
> If you have a number of
MPEG-2
> recordings that is entirely possible. I
> currently have 92 recordings listed in my `recorded` table (majority
> recorded from ivtv cards) with >400,000 records in `recordedseek`. You
> should notice that as your net number of stored recordings reduces so
> does the number of records in `recordedseek`. This table provides seek
> information for the recorded video streams.
>
> You may also have some orhpaned records in the `recordedseek` table -
> I'm not sure if this scenario is catered for by the database
> maintenance script.
The backend cleans it up.
> You can always run a SQL script comparing the
> records in `recorded` against the seek information in `recordedseek`.
But it's better left to Myth to manage the data. If you want to know
why, execute:
TRUNCATE TABLE recordedseek;
and then watch some TV.
Mike
More information about the mythtv-users
mailing list