Bug #78210 SHUTDOWN command should have an option to not dump buffer pool contents

Submitted:	25 Aug 2015 15:55	Modified:	21 Sep 2015 8:41
Reporter:	Morgan Tocker	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Server: Command-line Clients	Severity:	S4 (Feature request)
Version:	8.0+	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
The SHUTDOWN command introduced in 5.7.9 should support an option to not dump the buffer pool contents, which is now enabled by default in MySQL 5.7.

Via: http://dev.mysql.com/doc/refman/5.7/en/shutdown.html

This addresses this point mentioned in the comments from Bug #68863:

"I have also noticed that if you do a couple of successive shutdowns, perhaps due to a misconfiguration issue, you are likely to get mysqld to write out an incomplete buffer pool list as it hadn't had sufficient time to warm up completely."

How to repeat:
N/A

Suggested fix:
Add SHUTDOWN SKIP_BUFFER_POOL_DUMP

(Workaround viability is high because the setting innodb_buffer_pool_dump_at_shutdown is dynamic.  But a command may be useful.)

Hello Morgan,

Thank you for the feature request.

Thanks,
Umesh

Posted by developer:
 
Reported version value updated to reflect release name change from 5.8 to 8.0

Related
Bug #82181 	Shutdown command should have a reason

Also "SHUTDOWN SKIP BUFFER POOL DUMP" seems more SQL-like than "SHUTDOWN SKIP_BUFFER_POOL_DUMP".

Page generated in 0.042 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.