DROP TEMPORARY TABLE creates a transaction in binary log on read only server
Bug #1668602 reported by
Arturas Moskvinas
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| MySQL Server |
Unknown
|
Unknown
|
||||
| Percona Server moved to https://jira.percona.com/projects/PS | Status tracked in 5.7 | |||||
| 5.6 |
Fix Released
|
Medium
|
Laurynas Biveinis | |||
| 5.7 |
Fix Released
|
Medium
|
Laurynas Biveinis | |||
Bug Description
If "DROP TEMPORARY TABLE..." gets executed on server with GTID enabled and read_only mode enabled, then 'DROP /*!40005 TEMPORARY */ TABLE IF EXISTS `sometablename`' gets inserted in server binary log. This creates errant transaction, that other slaves in cluster might not have and can break replication if server with errant transaction gets promoted to master and this transaction is already deleted from binary logs.
Percona version tested: 5.6.35-80.0, Debian jessie
How to reproduce:
1. On any read-only server with non-privileged user execute "drop temporary table if exists `sometablename`", no need to actually create temporary table before dropping.
2. Check `show master status`, you'll find new gtid generated on slave in read-only mode
| description: | updated |
| description: | updated |
Revision history for this message
| Sveta Smirnova (svetasmirnova) wrote | #1 |
Revision history for this message
| Sveta Smirnova (svetasmirnova) wrote | #2 |
| Changed in percona-server: | |
| status: | New → Confirmed |
| tags: | added: upstream |
Revision history for this message
| Laurynas Biveinis (laurynas-biveinis) wrote | #3 |
Revision history for this message
| Arturas Moskvinas (arturas-w) wrote | #4 |
Revision history for this message
| Laurynas Biveinis (laurynas-biveinis) wrote | #5 |
Revision history for this message
| Laurynas Biveinis (laurynas-biveinis) wrote | #6 |
Revision history for this message
| Laurynas Biveinis (laurynas-biveinis) wrote | #7 |
Revision history for this message
| Laurynas Biveinis (laurynas-biveinis) wrote | #8 |
Revision history for this message
| Laurynas Biveinis (laurynas-biveinis) wrote | #9 |
Revision history for this message
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #10 |
To post a comment you must log in.
Thank you for the report.
Verified as described.