Details
-
Bug
-
Status: Stalled (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.5, 10.3(EOL), 10.4(EOL)
-
None
Description
According to the documentation (https://mariadb.com/kb/en/read-only-slaves/) changes to TEMPORARY TABLEs are no longer logged in the binary log:
CREATE, DROP, ALTER, INSERT and DELETE of temporary tables are not logged to binary log, even in statement or mixed mode. With earlier MariaDB versions, one can avoid the problem with temporary tables by using binlog_format=ROW in which cases temporary tables are never logged.
I don't think this is correct, imagin this:
CREATE TEMPORARY TABLE encrypt_the_password AS select id, username, MD5(password) FROM user;
|
INSERT INTO user_with_encryped_password SELECT * FROM encrypt_the_password;
|
The `user_with_encryped_password` table is a real table, and it cannot be filled if the temporary table does not exist in that session. Using SBR or MIXED replication, that is.
Is the documentation incorrect or is this a bug in the server?
Attachments
Issue Links
- is caused by
-
MDEV-17863 DROP TEMPORARY TABLE creates a transaction in binary log on read only server
- Closed