lp://staging/~percona-dev/percona-server/5.5.11-fix-bug-innodb_mysql_sync

Branch merges

Propose for merging

No branches dependent on this one.

Merged into lp://staging/~percona-dev/percona-server/5.5.11

Valentine Gostev: Pending requested 2011-04-20

Percona developers: Pending requested 2011-04-20

Diff: 14 lines (+7/-0)

1 file modified

mysql-test.diff (+7/-0)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Bug #758917: main.innodb_mysql_sync fails in 5.5.11

Undecided

Fix Released

Link a bug report

Related blueprints

109. By Oleg Tsarev on 2011-04-20

fix bug #758917, mysql bug http://lists.mysql.com/commits/134905

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.

105. By Alexey Kopytov on 2011-04-12

Fixed a test failure reported as bug #758926.

104. By Yasufumi Kinoshita <kinoyasu@rynex6> on 2011-04-12

fix bug756387, directly

103. By Alexey Kopytov on 2011-04-11

Fixed a test failure reported as bug #757602

102. By Alexey Kopytov on 2011-04-11

Bug #757749: main.handler_innodb fails in 5.5.11

Using ALTER TABLE to convert an InnoDB table to a MEMORY table could
fail due to a bug in innodb_expand_fast_index_creation.patch.

The problem in innodb_expand_fast_index_creation.patch was that for
ALTER TABLE ENGINE=... the code mistakenly made sure the original
table's engine is InnoDB, rather than the target's one. This resulted in
a failure if the target engine was MEMORY because it does not support
certain handler calls.

Fixed by making sure the target engine is InnoDB, not the original ones.

101. By Yasufumi Kinoshita <kinoyasu@rynex6> on 2011-04-11

fix bug756391, directly

100. By Alexey Kopytov on 2011-04-10

Fixed a test failure reported in bug #746513