Bug #85704 | mysql 8.0.x crashes when old-style trigger misses the "created" line in .TRG | ||
---|---|---|---|
Submitted: | 30 Mar 2017 8:54 | Modified: | 17 Apr 2017 14:27 |
Reporter: | Shane Bester (Platinum Quality Contributor) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Stored Routines | Severity: | S2 (Serious) |
Version: | 8.0.1 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[30 Mar 2017 8:54]
Shane Bester
[30 Mar 2017 22:20]
Jesper wisborg Krogh
Posted by developer: The workaround is: 1. Add as the last line (copied from sys/sys_config.TRG) to the .TRG file of the trigger with the missing created time (no spaces in front): created=149090559224 149090559224 2. Restart 8.0 - this fails with (expected): 2017-03-30T20:35:01.165251Z 1 [ERROR] Found partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again. ... 2017-03-30T20:35:01.431151Z 0 [ERROR] Data Dictionary initialization failed. 2017-03-30T20:35:01.431168Z 0 [ERROR] Aborting 3. Restart 8.0 again (to try upgrade again) - this time success. 4. Execute mysql_upgrade 5. Now the trigger data is working.
[17 Apr 2017 14:27]
Paul DuBois
Posted by developer: Noted in 8.0.2 changelog. An in-place MySQL upgrade failed if a .TRG file was missing the created line for the trigger definition. (This problem is unlikely to occur for upgrades to MySQL 8.0 from 5.7 because the created line is present for MySQL 5.7.2 and higher.)
[6 Oct 2018 8:21]
Truong Duong
Add create time doesn't help. I have to delete all .TRG file to a backup location then start mysql. I have to re-execute the create trigger statement after executed mysql_upgrade.
[6 Oct 2018 8:26]
MySQL Verification Team
That's surely a different bug to this one then. This bug is fixed in 8.0 GA versions.
[6 Oct 2018 8:38]
Truong Duong
Thanks Shane Bester, I will post other item for this.