Public bug reported: >From the MySQL manual:
http://dev.mysql.com/doc/refman/5.0/en/time-zone-leap-seconds.html 9.7.2. Time Zone Leap Second Support Before MySQL 5.0.74, if the operating system is configured to return leap seconds from OS time calls or if the MySQL server uses a time zone definition that has leap seconds, functions such as NOW() could return a value having a time part that ends with :59:60 or :59:61. If such values are inserted into a table, they would be dumped as is by mysqldump but considered invalid when reloaded, leading to backup/restore problems. As of MySQL 5.0.74, leap second values are returned with a time part that ends with :59:59. This means that a function such as NOW() can return the same value for two or three consecutive seconds during the leap second. It remains true that literal temporal values having a time part that ends with :59:60 or :59:61 are considered invalid. ** Affects: mysql-dfsg-5.0 (Ubuntu) Importance: Undecided Status: New ** Affects: mysql-dfsg-5.0 (Debian) Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #510177 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=510177 ** Also affects: mysql-dfsg-5.0 (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=510177 Importance: Unknown Status: Unknown -- mysql versions prior to 5.0.74 have trouble export/import with leap seconds https://bugs.launchpad.net/bugs/312345 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.0 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
