Bug #2830 Query cache does not work with --external-locking
Submitted: 16 Feb 2004 14:48 Modified: 5 Mar 2004 0:51
Reporter: Peter Zaitsev (Basic Quality Contributor) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:4.0 OS:Any (all)
Assigned to: Ingo Strüwing CPU Architecture:Any

[16 Feb 2004 14:48] Peter Zaitsev
Description:
Query cache seems not to catch table update done by different node in case 
--external-locking is used.

How to repeat:
Start 2 MySQL servers on same data files with --external-locking 

Node1:

create table mt(i int);

Node2:

mysql> set global query_cache_size=5000000;
Query OK, 0 rows affected (0.00 sec)

mysql> select * from mt;
Empty set (0.00 sec)

Node1: 

mysql> insert into mt values(1);
Query OK, 1 row affected (0.01 sec)

Node2:

mysql> select * from mt;
Empty set (0.00 sec)

mysql> select SQL_NO_CACHE * from mt;
+------+
| i    |
+------+
|    1 |
+------+
1 row in set (0.00 sec)
[5 Mar 2004 0:51] Michael Widenius
Thank you for your bug report. This issue has been addressed in the
documentation. The updated documentation will appear on our website
shortly, and will be included in the next release of the relevant
product(s).

Additional info:

I have now documented this issue.