Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
10.1(EOL), 10.2(EOL), 10.3(EOL), 10.4(EOL)
Description
commit c4bb7cd6dcd83a8c1dc15794d51cfacd10980855
Date: Thu Mar 20 00:59:13 2014 +0200
Fix for MDEV-5589: "Discrepancy in binlog on half-failed CREATE OR REPLACE"
'added code for not logging DROP TEMPORARY TABLE for tables where the CREATE TABLE was not logged. '
However the DROP query gets logged into binary log despite the fact of no CREATE was logged.
--connect (one,...)
|
set @@binlog_format=row;
|
drop temporary table if exists tt;
|
show binlog events; # =>
|
 |
| master-bin.000001 | 371 | Query | 1 | 485 | use `test`; DROP /*!40005 TEMPORARY */ TABLE IF EXISTS `tt` |
|
|
The connection close also create the DROP event in binlog.
Attachments
Issue Links
- relates to
-
MDEV-17863 DROP TEMPORARY TABLE creates a transaction in binary log on read only server
- Closed