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

paritioning not supported on transaction-precise versioned tabled

Details

    Description

      CREATE OR REPLACE TABLE inv (
      		 
         x INT,
      		 
         start_trxid BIGINT UNSIGNED GENERATED ALWAYS AS ROW START INVISIBLE,
      		 
         end_trxid BIGINT UNSIGNED GENERATED ALWAYS AS ROW END INVISIBLE,
      		 
         PERIOD FOR SYSTEM_TIME(start_trxid, end_trxid)
      		 
      ) WITH SYSTEM VERSIONING;
      		 
       
      		 
      alter table inv   PARTITION BY SYSTEM_TIME (
      		 
          PARTITION p_hist HISTORY,
      		 
          PARTITION p_cur CURRENT
      		 
        );
      		 
       
      		 
      ERROR 4110 (HY000): `start_trxid` must be of type TIMESTAMP(6) for system-versioned table `inv`

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-15951 system versioning by trx id doesn't work with partitioning

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-20271 Partitioned versioned tables do not accept Trx IDs

          • Major - Major loss of function.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. MDEV-23773 Cannot store the history separately for the transaction precise history tables.

          • Major - Major loss of function.
          • Open

          Activity

            No workflow transitions have been executed yet.

            People

              Unassigned Unassigned
              danblack Daniel Black
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

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