Bug #31747 Valgrind error in replication tree because engines does not set all null bits
Submitted: 22 Oct 2007 10:54 Modified: 15 Apr 2008 1:28
Reporter: Mats Kindahl Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: General Severity:S2 (Serious)
Version: OS:Any
Assigned to: Mats Kindahl CPU Architecture:Any

[22 Oct 2007 10:54] Mats Kindahl
See https://intranet.mysql.com/secure/pushbuild/getlog.pl?dir=mysql-5.1-new-rpl&entry=skozlov@...

The bug can potentially cause an update to not find the correct record and hence report an error that the record does not exist, while in fact it does.

How to repeat:
Just run the rpl_ndb_innodb2ndb test with valgrind on.

Suggested fix:
Initialize the unused bits of the record when returning it from a storage engine.
[15 Apr 2008 1:28] Paul DuBois
Noted in 5.1.23 changelog.

For tables with certain definitions, UPDATE statements could fail to
find the correct record to update and report an error when the
record did in fact exist.