Bug #17295 Unable to read REDO log

Submitted:	10 Feb 2006 8:14	Modified:	14 Feb 2006 8:52
Reporter:	Jonas Oreland	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S3 (Non-critical)
Version:	4.1,5.0,5.1	OS:
Assigned to:	Jonas Oreland	CPU Architecture:	Any

Description:
Zero page is incorrectly freed in LQH casuign corruption in REDO log in some
  circumstances

How to repeat:
 

Suggested fix:

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/2417

pushed into 5.0.19

pushed into 4.1.19

pushed into 5.1.7

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:

Bugfix documented in 4.1.19, 5.0.19, and 5.1.7 changelogs. Closed.

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/2724

Page generated in 0.055 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.