lp:~tsarev/percona-server/5.5.12-valgrind_786645_fixes

Branch merges

Propose for merging

No branches dependent on this one.

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Bug #786645: 5.5.12 valgrind warnings

Undecided

Fix Released

Link a bug report

Related blueprints

115. By Oleg Tsarev on 2011-06-07

Reason of bug: when we run test under valgrind test work long time, and slow query log has extra query "call mtr.check_testcase();".
I disable slow query log on startup, and enable only when I need.

114. By Laurynas Biveinis on 2011-06-06

Fix LP bug 791849: valgrind reported memory leaks in XtraDB
initialization.

The patch innodb_adaptive_hash_index_partitions.patch introduces
btr_search_latch_part and btr_search_sys->hash_index variables, which
are allocated in btr_search_sys_create, however corresponding
deallocation in btr_search_sys_free was incomplete. The fix is
straightforward.

113. By Alexey Kopytov on 2011-06-05

Bug #770296.

Fixed the test so that:

1. long_query_time is set 0 to capture all queries in the slow query
log to make the test more deterministic.
2. We can now get rid of using SLEEP() due to 1.
3. "# Time:" lines are skipped from the slow query log, because they are
added to the query log if the current time is different from the last
logged query time, which of course makes the test non-deterministic.

112. By Ignacio Nin on 2011-05-24

Adapt test to our directory names (debian, redhat)

This test expected documentation to be placed in /usr/share/doc/MySQL*.
Change the path in order to follow debian and RedHat's conventions.

111. By Ignacio Nin on 2011-05-18

Merge release branch, update version

Create release-5.5.12-20.3 with 5.5.12 changes and release branch from
5.5.11. Update versions to 5.5.12 and 20.3.

110. By Oleg Tsarev on 2011-05-11

port all non-Yasufumi patches

109. By kinoyasu <kinoyasu@gauntlet4> on 2011-05-10

port Yasufumi patches to 5.5.12

108. By Alexey Kopytov on 2011-04-20

LP bug #764395 / MySQL bug #60788: InnoDB crashes with an assertion
                                   failure when receiving a signal on
                                   pwrite()

The problem was that InnoDB I/O code was not fully conforming to the
standard on POSIX systems. fsync(), pread() and pwrite() calls may be
interrupted by a signal. In such a case, InnoDB would just fail with an
assertion failure rather than just restarting the interrupted call.

Fixed InnoDB I/O code so that the interrupted system calls are restarted
if they are interrupted by a signal.

107. By kinoyasu <kinoyasu@gauntlet4> on 2011-04-20

fix bug766236

106. By Yasufumi Kinoshita <kinoyasu@rynex6> on 2011-04-14

fix bug758891, directly.