4 commits

Author	SHA1	Message	Date
Davi Arnaut	a2e4449bfc	Bug#41098: Query Cache returns wrong result with concurrent insert ... The problem is that select queries executed concurrently with a concurrent insert on a MyISAM table could be cached if the select started after the query cache invalidation but before the unlock of tables performed by the concurrent insert. This race could happen because the concurrent insert was failing to prevent cache of select queries happening at the same time. The solution is to add a 'uncacheable' status flag to signal that a concurrent insert is being performed on the table and that queries executing at the same time shouldn't cache the results.	2009-02-19 18:09:35 -03:00
kent/mysqldev@mysql.com/production.mysql.com	fd1bd7547a	mysqld.cc: ... Corrects build problems embedded on Windows Makefile.am: Install .sym or mysqld-debug if exists query_cache_debug.test, query_cache_debug.result: Set more resonable query cache size (bug#35749) CMakeLists.txt: Added missing stacktrace.c	2008-04-02 00:43:17 +02:00
thek@adventure.(none)	77569d6708	Fixed faulty test case caused by race condition.	2008-01-11 14:16:46 +01:00
thek@adventure.(none)	3cd3a40d4d	Fixed test layout error.	2008-01-07 21:06:18 +01:00