[mythtv-users] 0.25 SQL CPU Load issues after optimisation

[Another Sillyname]

On 19 July 2012 21:48, Frans Grotepass <grotepass at gmail.com> wrote:
> On Thu, 19 Jul 2012 20:50:42 +0100
> Another Sillyname <anothersname at googlemail.com> wrote:
>
>> On 19 July 2012 20:33, Gary Buhrmaster <gary.buhrmaster at gmail.com>
>> wrote:
>> > On Thu, Jul 19, 2012 at 3:10 AM, Another Sillyname
>> > <anothersname at googlemail.com> wrote:
>> > ....
>> >> Thanks for this but didn't help I'm afraid.
>> >
>> > It might be interesting to take the select, and run it
>> > under an EXPLAIN (perhaps an extended explain)
>> > to see what might be the cause of (what sounds like)
>> > a table scan.
>> > _______________________________________________
>> > mythtv-users mailing list
>> > mythtv-users at mythtv.org
>> > http://www.mythtv.org/mailman/listinfo/mythtv-users
>>
>> I'm trying to reverse engineer the SQL command that appears to be the
>> trigger/cause of the the problem but I'm beyond the limit of my
>> skillset on SQL here.  It would be very helpful if either one of the
>> devs or a SQL guru stepped in here to help look at this.
>
> http://dev.mysql.com/doc/refman/5.1/en/slow-query-log.html
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://www.mythtv.org/mailman/listinfo/mythtv-users

Reading that it appears to just dump the command that takes more then
x seconds, I think we've already identified the command causing the
problem what I want to do now is understand what the command itself is
designed to do and why it's doing it.

As I said previously I'm not a SQL programmer but looking at the
command it seems on the surface at least to be overly complicated for
a single command execution.