mirror of
https://github.com/MariaDB/server.git
synced 2025-07-29 05:21:33 +03:00
BUG#11758263 50440: MARK UNORDERED UPDATE WITH AUTOINC UNSAFE
Problem: Statements that write to tables with auto_increment columns based on the selection from another table, may lead to master and slave going out of sync, as the order in which the rows are retrived from the table may differ on master and slave. Solution: We mark writing to a table with auto_increment table as unsafe. This will cause the execution of such statements to throw a warning and forces the statement to be logged in ROW if the logging format is mixed. Changes: 1. All the statements that writes to a table with auto_increment column(s) based on the rows fetched from another table, will now be unsafe. 2. CREATE TABLE with SELECT will now be unsafe.
This commit is contained in:
@ -1268,6 +1268,13 @@ public:
|
||||
*/
|
||||
BINLOG_STMT_UNSAFE_INSERT_SELECT_UPDATE,
|
||||
|
||||
/**
|
||||
Query that writes to a table with auto_inc column after selecting from
|
||||
other tables are unsafe as the order in which the rows are retrieved by
|
||||
select may differ on master and slave.
|
||||
*/
|
||||
BINLOG_STMT_UNSAFE_WRITE_AUTOINC_SELECT,
|
||||
|
||||
/**
|
||||
INSERT...REPLACE SELECT is unsafe because which rows are replaced depends
|
||||
on the order that rows are retrieved by SELECT. This order cannot be
|
||||
@ -1289,6 +1296,14 @@ public:
|
||||
*/
|
||||
BINLOG_STMT_UNSAFE_CREATE_REPLACE_SELECT,
|
||||
|
||||
/**
|
||||
CREATE TABLE...SELECT on a table with auto-increment column is unsafe
|
||||
because which rows are replaced depends on the order that rows are
|
||||
retrieved from SELECT. This order cannot be predicted and may differ on
|
||||
master and the slave
|
||||
*/
|
||||
BINLOG_STMT_UNSAFE_CREATE_SELECT_AUTOINC,
|
||||
|
||||
/**
|
||||
UPDATE...IGNORE is unsafe because which rows are ignored depends on the
|
||||
order that rows are updated. This order cannot be predicted and may differ
|
||||
|
Reference in New Issue
Block a user