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

Submitted: 19 May 2006 7:23 Modified: 13 Jun 2006 23:51
Reporter: Jonas Oreland Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:5.1 OS:
Assigned to: Jonas Oreland CPU Architecture:Any

[19 May 2006 7: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 11:39] Tomas Ulin 
pushed to 5.1.12
[13 Jun 2006 23: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.

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.054 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.