log-queries-not-using-indexes, found a possible culprit, and then ?

[SecondSight]

Hello !

I've not been able to optimize my server (I have many temp tables created on disk, some values are high (handler_read_rnd, table_locks_waited)) and so I'm searching further.

I've just enabled log-queries-not-using-indexes and now my mysql-slow.log file is full of this kind of lines :

# User@Host: xxxxxxx_forums[xxxxxxx_forums] @ localhost []
# Query_time: 0 Lock_time: 0 Rows_sent: 0 Rows_examined: 0
DELETE FROM ibf_sessions WHERE ip_address='188.165.12.134' OR running_time < 1278998248;
# User@Host: xxxxxxx_forums[xxxxxxx_forums] @ localhost []
# Query_time: 0 Lock_time: 0 Rows_sent: 0 Rows_examined: 0
DELETE FROM ibf_sessions WHERE ip_address='90.41.247.209' OR running_time < 1278998248;

What should I do now ?

Thank you ! :)

[SecondSight]

I also found this one :

# Query_time: 0 Lock_time: 0 Rows_sent: 1 Rows_examined: 4452
SELECT COUNT(*) as count FROM ibf_gallery_images i LEFT JOIN ibf_members m ON ( m.member_id=i.member_id )
LEFT JOIN ibf_gallery_albums a ON ( i.album_id=a.id )
LEFT JOIN ibf_gallery_ratings r ON ( r.img_id=i.id AND r.member_id=16850 ) WHERE ( i.category_id IN ( 16,12,13,15,14,30,40,39,48,49,47,50,21,6,20,32,10,37,4,2,27,45,22,41,42,29,33,23,35,44,34,28,46,26,24,25,43,5,36,38,8 ) OR i.album_id IN ( 1,3,5,7,8,9,11,17,27,31,32,33,35,54,47,49,50,56,62,67,122,69,72,76,83,84,87,174,93,103,106,112,116,117,118,119,120,121,126,130,138,235,152,154,163,166,171,173,175,176,182,180,204,206,26,222,95,82,98,189,92,96,104,109,128,159,146,135,139,140,141,142,143,144,151,155,160,164,165,168,169,170,237,179,205,191,192,194,195,196,200,203,208,209,210,211,212,218,225,230,231,232,234,238,239,242,244,245,43,44,156,158,190,185,198,220,215,216,217,219,221,224,233,227,236 ) ) AND i.approved=1;

[AlexJ]

Got same issue:

http://community.invisionpower.com/topic/313868-handler-read-rnd-next/

[SecondSight]

According to support these queries shouldn't be a problem and moreover, the query_time = 0 which shows that they are not an issue. :)