[MDEV-9173] REPLACE INTO not updating auto_increment correctly for galera cluster Created: 2015-11-24 Updated: 2018-07-16 Resolved: 2018-07-16 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Galera, Storage Engine - InnoDB |
| Affects Version/s: | 10.0.20-galera |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Mattias Mikkola | Assignee: | Jan Lindström (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Debian 7.8 |
||
| Issue Links: |
|
||||||||
| Description |
|
Similar to, but not exactly the same as http://bugs.mysql.com/bug.php?id=65116. Only shows up on cluster, standalone install work fine. Create the following table: Insert some data using REPLACE INTO: REPLACE INTO auto_inc (data) VALUES ('Hello'); SHOW TABLE STATUS LIKE 'auto_inc' shows Auto_increment set to 2. Issue the same query again: The row is now updated with id=2, but auto_increment is unchanged. On next insert this will result in duplicate key error. |
| Comments |
| Comment by Mattias Mikkola [ 2015-11-30 ] |
|
Found another, more recent, issue on the mysql tracker which seems more applicable: http://bugs.mysql.com/bug.php?id=73563 |
| Comment by Nirbhay Choubey (Inactive) [ 2015-12-01 ] |
|
|
| Comment by Mattias Mikkola [ 2015-12-01 ] |
|
However, our cluster has auto_increment_increment=1 since wsrep_auto_increment_controll=OFF |