lp:~tsarev/percona-server/fix_bug_851011_trace

Created by Oleg Tsarev on 2011-09-16 and last modified on 2011-09-18
Get this branch:
bzr branch lp:~tsarev/percona-server/fix_bug_851011_trace
Only Oleg Tsarev can upload to this branch. If you are Oleg Tsarev please log in for upload directions.

Branch merges

Related bugs

Related blueprints

Branch information

Recent revisions

204. By Oleg Tsarev on 2011-09-18

update mutex.patch

203. By Oleg Tsarev on 2011-09-18

update mutex.patch

202. By Oleg Tsarev on 2011-09-18

update mutex.patch

201. By Oleg Tsarev on 2011-09-18

update mutex.patch

200. By Oleg Tsarev on 2011-09-18

update mutex.patch

199. By Oleg Tsarev on 2011-09-18

update mutex.patch

198. By Oleg Tsarev on 2011-09-16

fix to bug #851011 & mutex.patch trace

197. By Oleg Tsarev on 2011-09-15

Add test-case for bug #851011: SHOW SLAVE STATUS NOLOCK acquire lock on some mutex.
Issue number: #12952.

196. By Oleg Tsarev on 2011-09-14

add ommited in revision 194 mysql-test/include/percona_row_based_replication_without_primary_key_delete.inc
fix bug #849849

195. By Alexey Kopytov on 2011-09-13

Bug #848703: innodb_fast_alter_column doesn't work with indexed columns

The problem was that when extending a column involved in an index,
mysql_alter_table() marked the corresponding index to be recreated
later (by adding it to both index_drop_buffer and
index_add_buffer). Such ALTER TABLE would normally be executed by
copying the table, because InnoDB would report incompatible metadata in
such a case.

However, due to innodb_fast_alter_column turned on, the metadata was
rightfully considered compatible, so the ALTER TABLE was executed
in-place, by first adding the indexes from index_add_buffer and then
dropping the ones from index_drop_buffer. Since in this case both drop
and add list contained the same index, InnoDB reported a duplicate index
name when trying to add the index. Reverting the order (i.e. dropping
before adding) would cause problems with foreign key constraints.

Fixed by changing compare_tables() so that, if innodb_fast_alter_column
is on, extending an index column does not lead to index being marked as
changed.

In addition, InnoDB no longer reports extending columns as compatible
metadata when innodb_fast_alter_column is OFF. This was the reasons why
the bug occurred even with disabled feature.

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
Stacked on:
lp:percona-server/5.5
This branch contains Public information 
Everyone can see this information.

Subscribers