Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
N/A
-
None
Description
If a system-versioned (timestamp-based) table is created on pre-11.4 server, its current records have the row_end within 2038-01.
It doesn't change upon live upgrade to the server with the extended timestamp, even after running mysql_upgrade, and thus these records become historical.
Also, if mysqldump --dump-history is run on the old version, it again contains 2038-01 for current records, so restoring this dump doesn't help either. If mysqldump is run without --dump-history, it works (for invisible columns at least), but then all versioning history will be lost.
Attachments
Issue Links
- is caused by
-
MDEV-32188 make TIMESTAMP use whole 32-bit unsigned range
- Closed