[MDEV-13074] AliSQL: [Feature] Issue #42 Persistent AUTO_INCREMENT value for InnoDB table Created: 2017-06-13  Updated: 2017-11-17  Resolved: 2017-11-17

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Fix Version/s: 10.2.4, 10.3.0

Type: Task Priority: Major
Reporter: Sergey Vojtovich Assignee: Marko Mäkelä
Resolution: Duplicate Votes: 0
Labels: None

Issue Links:
Duplicate
duplicates MDEV-6076 Persistent AUTO_INCREMENT for InnoDB Closed
Epic Link: AliSQL patches

 Description    

InnoDB auto_increment value is not persistent and can lead to some
 
values reused, as described by official bug #199.
 
 
 
This patch fix the problem by writing the last used AUTO_INCREMENT
 
to the root page of the clustered index, using the PAGE_MAX_TRX_ID
 
field, which is unused for root page.
 
 
 
Two InnoDB variables are introduced to control this persistent behaviour:
 
- innodb_autoinc_persistent
 
  This persistent behaviour is enabled or not.
 
 
 
- innodb_autoinc_persistent_interval
 
  The interval of persist max auto_increment value.

https://github.com/alibaba/AliSQL/commit/02a52074a637303a6b298b5f452b7673830f3ad8

 Comments   
Comment by Marko Mäkelä [ 2017-11-17 ]

MDEV-6076 implemented persistent AUTO_INCREMENT in MariaDB 10.2.4 (and 10.3.0).

Generated at Thu Feb 08 08:02:42 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.