Bug #45312 FLUSH TIMEZONES to reload timezone info into MySQL server
Submitted: 3 Jun 2009 21:19
Reporter: Guilhem Bichot Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server Severity:S4 (Feature request)
Version: OS:Any
Assigned to: Mark Leith CPU Architecture:Any

[3 Jun 2009 21:19] Guilhem Bichot
Description:
As is policy in the MMCF group, this bug report will be a central place to track status and communications about this feature for which Mark has created a patch.
To satisfy internal processes of documenting design, passing architecture review etc, there is also a Worklog entry at http://forge.mysql.com/worklog/task.php?id=4908.
Description:
Sometimes (rarely; the known case happened in 2006) there are changes in
timezones (in 2006, DST lasted much longer than usual per a decision of Congress
as explained in 
http://www.npr.org/templates/story/story.php?storyId=6393658 ).
For the MySQL Server (mysqld) to learn about the corrected timezone, depending
on the setup it needs to be notified either after an upgrade of the OS' timezone
info or after an upgrade of the mysql.time_zone* tables. A simple way to do this
is to restart mysqld but it also kills any mysqld's cache (MyISAM key cache,
Query Cache, etc) so mysqld will be slow after restart, which should be avoided
under production.
To avoid this, Mark Leith proposes a patch which implements a "FLUSH TIMEZONES"
command, which one can issue instead of restarting mysqld.

How to repeat:
feature request, nothing to repeat

Suggested fix:
reviews by email at:
http://lists.mysql.com/internals/36575
http://lists.mysql.com/internals/36692
[3 Jun 2009 21:20] Guilhem Bichot
Patch is in the worklog entry in "low level design"