Bug #4259 | minimum query_cache_size value required | ||
---|---|---|---|
Submitted: | 23 Jun 2004 11:14 | Modified: | 27 May 2005 14:33 |
Reporter: | Mickael Besson | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server | Severity: | S4 (Feature request) |
Version: | 3.0.14 & MySQL 5.0 & j2sdk1.4.2_04 | OS: | Windows (Windows NT4) |
Assigned to: | Alexey Botchkov | CPU Architecture: | Any |
[23 Jun 2004 11:14]
Mickael Besson
[23 Jun 2004 12:29]
Mickael Besson
The cause of this error is that in my.ini there was : query_cache_size= 64M query_cache_limit = 4M instead of query_cache_size= 64 query_cache_limit = 4M Endeed query_cache_size should not contain 'M', and it isn't very logical. You should ameliorate this (all or nothing). Thank you.
[23 Jun 2004 21:53]
Mark Matthews
This appears to be a server-side bug. You can crash MySQL-5.0 (even the latest from BitKeeper) from JDBC or the MySQL command-line client with the following sequence of queries (which is the sequence of queries the JDBC driver is doing as part of its initialization sequence): Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 2 to server version: 5.0.1-alpha-log Type 'help;' or '\h' for help. Type '\c' to clear the buffer. mysql> SET character_set_results = NULL; Query OK, 0 rows affected (0.00 sec) mysql> select round('inf'), round('-inf'), round('nan'); ERROR 2013 (HY000): Lost connection to MySQL server during query
[27 May 2005 14:33]
Alexey Botchkov
Tried with the last 5.0.7 on WinXP both query cache settings and queries by Matthews worked ok