Am 23.07.2012 16:37, schrieb Ananda Kumar: > why dont u setup a staging env, which is very much similar to your > production and tune all long running sql >
They are tuned and they are fast :) but the never logout and therefore the time get accumulated. re, wh > On Mon, Jul 23, 2012 at 8:02 PM, walter harms <wha...@bfs.de> wrote: > >> >> >> Am 23.07.2012 16:10, schrieb Ananda Kumar: >>> you can check the slow query log, this will give you all the sql's which >>> are taking more time to execute >>> >> >> Yes but you will see the results only when the query is finished. >> my first idea was to use something like this: >> select * from information_schema.processlist where state like 'executing' >> and time > 1000 ; >> >> unfortunately time i cumulative and i would kill long running processes >> that we have also. >> i guess i will make some assumptions about the statement and kill the rest. >> >> re, >> wh >> >> >>> On Mon, Jul 23, 2012 at 7:38 PM, walter harms <wha...@bfs.de> wrote: >>> >>>> >>>> >>>> Am 23.07.2012 15:47, schrieb Ananda Kumar: >>>>> you can set this is in application server. >>>>> You can also set this parameter in my.cnf >>>>> wait_timeout=120 in seconds. >>>>> But the above parameter is only for inactive session >>>>> >>>> >>>> >>>> acutualy i want to catch scripts running wild. >>>> >>>> re, >>>> wh >>>> >>>>> >>>>> On Mon, Jul 23, 2012 at 6:18 PM, walter harms <wha...@bfs.de> wrote: >>>>> >>>>>> Hi list, >>>>>> is there a switch where i can restrict the connect/execution time for >> a >>>>>> query ? >>>>>> >>>>>> re, >>>>>> wh >>>>>> >>>>>> -- >>>>>> MySQL General Mailing List >>>>>> For list archives: http://lists.mysql.com/mysql >>>>>> To unsubscribe: http://lists.mysql.com/mysql >>>>>> >>>>>> >>>>> >>>> >>> >> > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql
