Bug #3333 Manual incorrectly describes how FLUSH TABLES operates with query cache

Submitted:	30 Mar 2004 4:48	Modified:	30 Mar 2004 8:46
Reporter:	Victoria Reznichenko	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Documentation	Severity:	S3 (Non-critical)
Version:		OS:
Assigned to:	Documentation Team	CPU Architecture:	Any

Description:
In the manual mentioned:

You can defragment the query cache to better utilize its memory with the FLUSH QUERY CACHE statement. The statement does not remove any queries from the cache. The FLUSH TABLES statement also flushes the query cache. 

http://www.mysql.com/doc/en/Query_Cache_Status_and_Maintenance.html

Looking in the mysqladmin extended-status output I can see that
FLUSH TABLES works as RESET QUERY CACHE statement, it removes all queries from the cache.

How to repeat:
Run mysqladmin extended-status before and after FLUSH TABLES command.

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).

Page generated in 0.048 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.