Bug #89584 5.7->8.0 upgrade crash with default-time-zone set
| Submitted: | 8 Feb 2018 8:39 | Modified: | 2 Mar 2018 19:57 |
|---|---|---|---|
| Reporter: | Shane Bester (Platinum Quality Contributor) | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Data Dictionary | Severity: | S1 (Critical) |
| Version: | 8.0.4 | OS: | Any |
| Assigned to: | CPU Architecture: | Any |
[8 Feb 2018 8:39]
Shane Bester
[2 Mar 2018 19:57]
Daniel Price
Posted by developer: Fixed as of the upcoming 8.0.5 release, and here's the changelog entry: After upgrading from MySQL 5.7 to MySQL 8.0, the first attempt to start the server on a MySQL 5.7 data directory with --default-time-zone set to a specific time value such as "+00:00" caused the server to exit.
[19 Mar 2018 12:39]
Daniel Price
Posted by developer: The changelog entry now appears in the 8.0.11 release notes.
[29 Aug 2018 13:55]
Daniel Price
Posted by developer: Test-related post fix changed. No changes to the 8.0.11 changelog entry.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.051 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.