Dear:
A open source development community for unix-like systems.
http://dev.unix-like.net http://dev.unix-like.net/
Thanks.
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
A director s term ends in a given year, but at no given time of year; depends
on the yearly meeting.
I thought I would try YEAR to record it--but, in spite of
http://dev.mysql.com/doc/refman/5.5/en/year.html , simply assigning NOW() to
such a type does not work. There is also no implicit
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
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
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,
you can check the slow query log, this will give you all the sql's which
are taking more time to execute
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
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
why dont u setup a staging env, which is very much similar to your
production and tune all long running sql
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
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
so. its more of inactive connections, right.
What do you mean by NEVER LOGOUT
On Mon, Jul 23, 2012 at 8:17 PM, walter harms wha...@bfs.de wrote:
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
Am 23.07.2012 16:58, schrieb Ananda Kumar:
so. its more of inactive connections, right.
What do you mean by NEVER LOGOUT
The programms watch certain states in the database,
the connect automatic at db startup, disconnecting
is an error case.
re,
wh
On Mon, Jul 23, 2012 at 8:17 PM,
Am 23.07.2012 17:35, schrieb walter harms:
Am 23.07.2012 16:58, schrieb Ananda Kumar:
so. its more of inactive connections, right.
What do you mean by NEVER LOGOUT
The programms watch certain states in the database,
the connect automatic at db startup, disconnecting
is an error
not very clear. You use connection pooling, right.
If the same session/thread is held for long time, it means the thread is
not getting closed even after doing its job, and adding to execution time.
On Mon, Jul 23, 2012 at 9:05 PM, walter harms wha...@bfs.de wrote:
Am 23.07.2012 16:58,
Am 23.07.2012 17:38, schrieb Reindl Harald:
Am 23.07.2012 17:35, schrieb walter harms:
Am 23.07.2012 16:58, schrieb Ananda Kumar:
so. its more of inactive connections, right.
What do you mean by NEVER LOGOUT
The programms watch certain states in the database,
the connect automatic
mysql SELECT YEAR(NOW());
+-+
| YEAR(NOW()) |
+-+
|2012 |
+-+
mysql SELECT CONCAT('2012', '-01-01');
+--+
| CONCAT('2012', '-01-01') |
+--+
| 2012-01-01 |
+--+
To
And don't kill replication when you see a big time in processlist.
therefore the time get accumulated
?? Each query stands alone in timing. The idle time is caught by
wait_timeout, which was already mentioned. You can distinguish the cases by
whether processlist says Sleep.
A Sleeping
Hello everyone.
Today I restarted a server and got this at the log file:
InnoDB: The InnoDB memory heap is disabled
I read a little (maybe to little) about and it says something about the
native use of malloc.
The system is a linux
Linux 2.6.34.7-0.7 #1 SMP PREEMPT 2010-12-13 11:13:53 +0100
17 matches
Mail list logo