Bug #92492 log_error_verbosity - startup and shutdown messages

• Submitted: 19 Sep 2018 7:58
• Modified: 23 Oct 2019 15:06
• Reporter: Rafael Bos
• Status: Not a Bug
• Category: MySQL Server
• Severity: S4 (Feature request)
• Version: 5.7.22
• OS: Red Hat
• CPU Architecture: x86

[19 Sep 2018 7:58] Rafael Bos

Description:
Version 5.7 with the log_error_verbosity parameter behaves somewhat differently than previous versions with log_warnings, at least when it comes to startup and shutdown messages
Having log_error_verbosity set to 2 all startup and shutdown messages - examples below - are suppressed, probably due to the fact that those are of level 'Note' 

Starting mysqld daemon with databases from 
Server hostname (bind-address): 'A.B.C.D'; port: AAAA
Server socket created on IP: 'A.B.C.D'.
mysqld: ready for connections.
mysqld: Normal shutdown
Shutting down slave threads
Forcefully disconnecting X remaining clients
Binlog end
Shutting down plugin 'name'
mysqld: Shutdown complete

How to repeat:
Set log_error_verbosity to 3 - startup/shutdown messages are logged
Set log_error_verbosity to 2 or below - startup/shutdown messages are not logged

Suggested fix:
Keep (all/selected) startup and shutdown messages logged with any value for log_error_verbosity, either by default or with a new parameter that would turn that on/off

[23 Oct 2019 15:06] MySQL Verification Team

Hi Mr. Bos,

Thank you for your feature request.

Unfortunately, log_error_verbosity works exactly how it is intended to. That is how a vast majority of our customers and users wanted it to work.

Your feature request could be considered, but not for 5.7. Only for 8.0. However, even then, your feature request has to be defined very, very precisely ......... Preferably, you should show by example what would latest 8.0 release print in the error log and what should not be printed.