Description:
In MySQL 5.7.11 or later, mysqld_safe can use mysqld-safe-log-timestamps option.
https://bugs.mysql.com/bug.php?id=78475
http://dev.mysql.com/doc/refman/5.7/en/mysqld-safe.html#option_mysqld_safe_mysqld-safe-log...
If mysqld use log_timestamps=SYSTEM, it become +09:00 for mysqld in Japan(JST: Japan Standard Time), but mysqld_safe don't read that's setting, like this.
2016-10-27T14:32:50.908131+09:00 0 [Note] Shutting down plugin 'binlog'
2016-10-27T14:32:50.909034+09:00 0 [Note] /usr/sbin/mysqld: Shutdown complete
2016-10-27T05:32:50.923729Z mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
2016-10-27T05:33:29.501085Z mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
As you know, I can avoid this problem with setting to mysqld-safe-log-timestamps=SYSTEM. But it seems that *Redundancy* setting. Almost of all users want to the same time-stamp settings based on mysqld's setting.
How to repeat:
(1) Set log_timestamps=SYSTEM in my.cnf[mysqld] in Japanese Linux.
Suggested fix:
Can we make a default value 'auto' for mysqld-safe-log-timestamps, and if there is no mysqld-safe-log-timestamps, use log-timestamps setting for mysqld-safe-log-timestamps ?
