Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-33032

Live and dump upgrade from previous versions to the extended timestamp fails for system-versioned tables

    XMLWordPrintable

Details

    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

          Activity

            People

              monty Michael Widenius
              elenst Elena Stepanova
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.