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
-
Activity
Field | Original Value | New Value |
---|---|---|
Link |
This issue relates to |
Assignee | Andrei Elkin [ elkin ] |
Component/s | Replication [ 10100 ] |
Labels | temporary-table-replication |
Status | Open [ 1 ] | In Progress [ 3 ] |
Assignee | Andrei Elkin [ elkin ] | Sujatha Sivakumar [ sujatha.sivakumar ] |
Affects Version/s | 10.1 [ 16100 ] |
issue.field.resolutiondate | 2019-07-25 06:23:16.0 | 2019-07-25 06:23:16.822 |
Fix Version/s | 10.1.41 [ 23406 ] | |
Fix Version/s | 10.3.17 [ 23411 ] | |
Fix Version/s | 10.4.7 [ 23720 ] | |
Resolution | Fixed [ 1 ] | |
Status | In Progress [ 3 ] | Closed [ 6 ] |
Workflow | MariaDB v3 [ 98333 ] | MariaDB v4 [ 156492 ] |
Zendesk Related Tickets | 180166 |