Bug #45825 INSERT DELAYED is not unsafe: logged in statement format
| Submitted: | 29 Jun 2009 14:55 | Modified: | 3 Sep 2010 17:20 |
|---|---|---|---|
| Reporter: | Sven Sandberg | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Replication | Severity: | S2 (Serious) |
| Version: | 5.1+ | OS: | Any |
| Assigned to: | Sven Sandberg | CPU Architecture: | Any |
[29 Jun 2009 14:55]
Sven Sandberg
[13 Jul 2009 11:11]
Sven Sandberg
In fact, the bug is even more serious than reported above. INSERT DELAYED is not even logged in row format if binlog_format=MIXED (run the above test case to see). Changing bug title accordingly.
[18 Jan 2010 12:06]
Bugs System
Pushed into 6.0.14-alpha (revid:alik@ibmvm-20100118120357-hnzhgadkpzqfnvsc) (version source revid:alik@ibmvm-20100118115413-kd3klpine09yyktw) (merge vers: 6.0.14-alpha) (pib:16)
[18 Jan 2010 12:07]
Bugs System
Pushed into mysql-next-mr (revid:alik@ibmvm-20100118120111-73dulkgc893it4r9) (version source revid:alik@ibmvm-20100118115335-0stecyzftqm7bqx6) (pib:16)
[18 Jan 2010 14:27]
Jon Stephens
DOcumented bugfix in the 5.6.0 and 6.0.14 changelogs as follows:
Even though INSERT DELAYED statements are unsafe for
statement-based replication, they caused the statement only to
be logged in row format when the binary logging format was
MIXED, but did not cause a warning to be generated when the
binary logging format was STATEMENT.
Waiting for other merges to 5.1+, set status NDI.
[6 Mar 2010 11:00]
Bugs System
Pushed into 5.5.3-m3 (revid:alik@sun.com-20100306103849-hha31z2enhh7jwt3) (version source revid:vvaintroub@linux-rbsx-20100118220048-5vnyqi5ghsbgmdsd) (merge vers: 5.5.99-m3) (pib:16)
[7 Mar 2010 2:13]
Paul DuBois
Moved 5.6.0 changelog entry to 5.5.3. Setting report to Need Merge pending push to 5.1.x.
[3 Sep 2010 17:20]
Jon Stephens
Need Merge status appears to have been set in error; closing.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.065 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.