in STATEMENT replication empty transactions are replicated

Bug #914892 reported by Seppo Jaakola on 2012-01-11
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL patches by Codership
High
Seppo Jaakola
5.5
High
Seppo Jaakola
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC
Status tracked in 5.6
5.5
Incomplete
Undecided
Unassigned
5.6
Incomplete
Undecided
Unassigned

Bug Description

when binlog format is set to STATEMENT and an empty tranaction commits, it will happen that transaction ID allocated for such transactions is always -1. If two such transactions commit at same time, replicator will have issues to deal with two transactions having same ID.

Changed in codership-mysql:
importance: Undecided → Medium
assignee: nobody → Seppo Jaakola (seppo-jaakola)
milestone: none → 5.5.17-22.4
Changed in codership-mysql:
milestone: 5.5.33-23.7.6 → 5.5.34-24.9
tags: added: statement
Changed in codership-mysql:
milestone: 5.5.34-25.9 → 5.5.34-25.10
Changed in codership-mysql:
milestone: 5.5.37-25.10 → 5.5.37-25.11
Krunal Bauskar (krunal-bauskar) wrote :

Do we have reproducible scenario ?

What effect do we observe (crash/in-consistency) ?

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1197

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers