Bug #19928 Uncommitted transaction enter checkpoint/backup, making it inconsistent

• Submitted: 19 May 2006 9:23
• Modified: 14 Jun 2006 1:51
• Reporter: Jonas Oreland
• Status: Closed
• Category: Server: Cluster
• Severity: S3 (Non-critical)
• Version: 5.1
• Assigned to: Jonas Oreland

[19 May 2006 9:23] Jonas Oreland

Description:
backup (lcp) uses comittedread tup scan.
this did not check if row was in state "ALLOC", meaning that it was an uncomitted
insert.
this row could end up in checkpoint/backup...

How to repeat:
 

Suggested fix:

[12 Jun 2006 13:39] Tomas Ulin

pushed to 5.1.12

[14 Jun 2006 1:51] Jon Stephens

Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html

Additional info:

Documented bugfix in 5.1.12 changelog. Closed.