~drizzle-trunk/drizzle/development : changes

~drizzle-trunk/drizzle/development » Changes from revision 1819.7.61

Rev	Summary	Authors	Date
1819.7.61	Merge Revision revid:marko.makela@oracle.com-20100629131219-... Merge Revision revid:marko.makela@oracle.com-20100629131219-pjbkpk5rsqztmw27 from MySQL InnoDB Original revid:marko.makela@oracle.com-20100629131219-pjbkpk5rsqztmw27 Original Authors: Marko Mäkelä <marko.makela@oracle.com> Original commit message: ChangeLog entry for Bug #54408	Marko Mäkelä	14 years ago
1819.7.60	Merge Revision revid:marko.makela@oracle.com-20100629130058-... Merge Revision revid:marko.makela@oracle.com-20100629130058-1ilqaj51u9sj9vqe from MySQL InnoDB Original revid:marko.makela@oracle.com-20100629130058-1ilqaj51u9sj9vqe Original Authors: Marko Mäkelä <marko.makela@oracle.com> Original commit message: Bug#54408: txn rollback after recovery: row0umod.c:673 dict_table_get_format(index->table) The REDUNDANT and COMPACT formats store a local 768-byte prefix of each externally stored column. No row_ext cache is needed, but we initialized one nevertheless. When the BLOB pointer was zero, we would ignore the locally stored prefix as well. This triggered an assertion failure in row_undo_mod_upd_exist_sec(). row_build(): Allow ext==NULL when a REDUNDANT or COMPACT table contains externally stored columns. row_undo_search_clust_to_pcur(), row_upd_store_row(): Invoke row_build() with ext==NULL on REDUNDANT and COMPACT tables. rb://382 approved by Jimmy Yang	Marko Mäkelä	14 years ago
1819.7.59	Merge Revision revid:marko.makela@oracle.com-20100629125653-... Merge Revision revid:marko.makela@oracle.com-20100629125653-t799e5x30h31cvrd from MySQL InnoDB Original revid:marko.makela@oracle.com-20100629125653-t799e5x30h31cvrd Original Authors: Marko Mäkelä <marko.makela@oracle.com> Original commit message: ChangeLog entry for Bug #54358	Marko Mäkelä	14 years ago
1819.7.58	Merge Revision revid:marko.makela@oracle.com-20100629125518-... Merge Revision revid:marko.makela@oracle.com-20100629125518-m3am4ia1ffjr0d0j from MySQL InnoDB Original revid:marko.makela@oracle.com-20100629125518-m3am4ia1ffjr0d0j Original Authors: Marko Mäkelä <marko.makela@oracle.com> Original commit message: Bug#54358: READ UNCOMMITTED access failure of off-page DYNAMIC or COMPRESSED columns When the server crashes after a record stub has been inserted and before all its off-page columns have been written, the record will contain incomplete off-page columns after crash recovery. Such records may only be accessed at the READ UNCOMMITTED isolation level or when rolling back a recovered transaction in recv_recovery_rollback_active(). Skip these records at the READ UNCOMMITTED isolation level. TODO: Add assertions for checking the above assumptions hold when an incomplete BLOB is encountered. btr_rec_copy_externally_stored_field(): Return NULL if the field is incomplete. row_prebuilt_t::templ_contains_blob: Clarify what "BLOB" means in this context. Hint: MySQL BLOBs are not the same as InnoDB BLOBs. row_sel_store_mysql_rec(): Return FALSE if not all columns could be retrieved. Previously this function always returned TRUE. Assert that the record is not delete-marked. row_sel_push_cache_row_for_mysql(): Return FALSE if not all columns could be retrieved. row_search_for_mysql(): Skip records containing incomplete off-page columns. Assert that the transaction isolation level is READ UNCOMMITTED. rb://380 approved by Jimmy Yang	Marko Mäkelä	14 years ago
1819.7.57	Merge Revision revid:davi.arnaut@oracle.com-20100720173615-y... Merge Revision revid:davi.arnaut@oracle.com-20100720173615-yc08nbtrfxsuh8mb from MySQL InnoDB Just merging test case for Drizzle Original revid:davi.arnaut@oracle.com-20100720173615-yc08nbtrfxsuh8mb Original Authors: Davi Arnaut <davi.arnaut@oracle.com> Original commit message: Bug#54453: Failing assertion: trx->active_trans when renaming a table with active trx Essentially, the problem is that InnoDB does a implicit commit when a cursor (table handler) is unlocked/closed, creating a dissonance between the transaction state within the server layer and the storage engine layer. Theoretically, a statement transaction can encompass several table instances in a similar manner to a multiple statement transaction, hence it does not make sense to limit a statement transaction to the lifetime of the table instances (cursors) used within it. Since this particular instance of the problem is only triggerable on 5.1 and is masked on 5.5 due 2PC being skipped (assertion is in the prepare phase of a 2PC), the solution (which is less risky) is to explicitly end the transaction before the cached table is unlock on rename table. The patch is to be null merged into trunk.	Davi Arnaut	14 years ago
1819.7.56	remove innodb test as we don't have bad data being accepted remove innodb test as we don't have bad data being accepted	Stewart Smith	14 years ago
1819.7.55	Merge Revision revid:build@mysql.com-20100622200931-wphbrypu... Merge Revision revid:build@mysql.com-20100622200931-wphbrypulhqvm4ep from MySQL InnoDB Original revid:build@mysql.com-20100622200931-wphbrypulhqvm4ep Original Authors: MySQL Build Team<build@mysql.com> Original commit message: Backport into 5.1.46sp1: > revno: 3351.14.56 > committer: Marko Mdkeld <marko.makela@oracle.com> > branch nick: 5.1-innodb > timestamp: Mon 2010-04-26 14:08:56 +0300 > message: > Add a test case for Bug #52745.	MySQL Build Team	14 years ago
1819.7.54	Merge Revision revid:build@mysql.com-20100622195935-i5cctxht... Merge Revision revid:build@mysql.com-20100622195935-i5cctxhtgganeuxr from MySQL InnoDB Original revid:build@mysql.com-20100622195935-i5cctxhtgganeuxr Original Authors: MySQL Build Team<build@mysql.com> Original commit message: Backport into build-201006221614-5.1.46sp1 > ------------------------------------------------------------ > revno: 3351.14.47 > revision-id: marko.makela@oracle.com-20100421095033-0acvzxb8um8cms0a > parent: marko.makela@oracle.com-20100421094032-ir4glqk46qvg2ywn > committer: Marko Mkel <marko.makela@oracle.com> > branch nick: 5.1-innodb > timestamp: Wed 2010-04-21 12:50:33 +0300 > message: > dtuple_convert_big_rec(): Store locally any fields whose maximum length > is less than 256 bytes. (Bug #52745) > Add related comments and debug assertions to the "offsets" > functions in rem0rec.c. > Approved by Sunny Bains	MySQL Build Team	14 years ago
1819.7.53	Merge Revision revid:build@mysql.com-20100622195047-sddeu498... Merge Revision revid:build@mysql.com-20100622195047-sddeu4986bbxhkl7 from MySQL InnoDB Original revid:build@mysql.com-20100622195047-sddeu4986bbxhkl7 Original Authors: MySQL Build Team<build@mysql.com> Original commit message: Backport into build-201006221614-5.1.46sp1 > ------------------------------------------------------------ > revno: 3351.14.50 > revision-id: marko.makela@oracle.com-20100421185359-8qaxoa2yyrpzwdd7 > parent: marko.makela@oracle.com-20100421102723-0i80uezbyu0ekj5d > committer: Marko Mkel <marko.makela@oracle.com> > branch nick: 5.1-innodb > timestamp: Wed 2010-04-21 21:53:59 +0300 > message: > btr_page_split_and_insert(): Avoid an infinite loop. (Bug #52964) > > btr_page_tuple_smaller(): New function, refactored from > btr_page_split_and_insert(). > > btr_page_get_split_rec(): Renamed from btr_page_get_sure_split_rec(). > Note that a NULL return may mean that the tuple is to be inserted into > either the lower or upper page, to be determined by btr_page_tuple_smaller(). > > btr_page_split_and_insert(): When btr_page_get_split_rec() returns NULL, > invoke btr_page_tuple_smaller() to determine which half-page the tuple > belongs to. > > Reviewed by Sunny Bains	MySQL Build Team	14 years ago
1819.7.52	fix test result fix test result	Stewart Smith	14 years ago
1819.7.51	add missing test for Innobase http://bugs.mysql.com/54044 add missing test for Innobase http://bugs.mysql.com/54044	Stewart Smith	14 years ago
1819.7.50	Merge Revision revid:karen.langford@oracle.com-2010070912234... Merge Revision revid:karen.langford@oracle.com-20100709122348-pbgrcz2zgvzlqzld from MySQL InnoDB Original revid:karen.langford@oracle.com-20100709122348-pbgrcz2zgvzlqzld Original Authors: karen.langford@oracle.com Original commit message: Fix bug #55039 Failing assertion: space_id > 0 in fil0fil.c.	karen.langford at or...	14 years ago
1819.7.49	Merge Revision revid:sunny.bains@oracle.com-20100625081841-p... Merge Revision revid:sunny.bains@oracle.com-20100625081841-ppulnkjk1qlazh82 from MySQL InnoDB Original revid:sunny.bains@oracle.com-20100625081841-ppulnkjk1qlazh82 Original Authors: Sunny Bains <Sunny.Bains@Oracle.Com> Original commit message: Fix bug#54583. This change reverses rsvn:1350 by getting rid of a bogus assertion and clarifies the invariant in dict_table_get_on_id(). In Mar 2007 Marko observed a crash during recovery, the crash resulted from an UNDO operation on a system table. His solution was to acquire an X lock on the data dictionary, this in hindsight was an overkill. It is unclear what caused the crash, current hypothesis is that it was a memory corruption. The X lock results in performance issues by when undoing changes due to rollback during normal operation on regular tables. Why the change is safe: ====================== The InnoDB code has changed since the original X lock change was made. In the new code we always lock the data dictionary in X mode during startup when UNDOing operations on the system tables (this is a given). This ensures that the crash Marko observed cannot happen as long as all transactions that update the system tables follow the standard rules by setting the appropriate DICT_OP flag when writing the log records when they make the changes. If transactions violate the above mentioned rule then during recovery (at startup) the rollback code (see trx0roll.c) will not acquire the X lock and we will see the crash again. This will however be a different bug.	Sunny Bains	14 years ago
1819.7.48	Merge Revision revid:inaam.rana@oracle.com-20100624124450-2m... Merge Revision revid:inaam.rana@oracle.com-20100624124450-2m3mg1238ewvakgx from MySQL InnoDB Original revid:inaam.rana@oracle.com-20100624124450-2m3mg1238ewvakgx Original Authors: Inaam Rana <inaam.rana@oracle.com> Original commit message: Add ChangeLog for bug#39168	Inaam Rana	14 years ago
1819.7.47	Merge Revision revid:marko.makela@oracle.com-20100624104820-... Merge Revision revid:marko.makela@oracle.com-20100624104820-p4ojmxcmq8qeos6d from MySQL InnoDB Original revid:marko.makela@oracle.com-20100624104820-p4ojmxcmq8qeos6d Original Authors: Marko Mäkelä <marko.makela@oracle.com> Original commit message: Add ChangeLog entry for Bug#54679	Marko Mäkelä	14 years ago
1819.7.46	Merge Revision revid:jimmy.yang@oracle.com-20100623023920-l7... Merge Revision revid:jimmy.yang@oracle.com-20100623023920-l74rw5x4y35o81rl from MySQL InnoDB Original revid:jimmy.yang@oracle.com-20100623023920-l74rw5x4y35o81rl Original Authors: Jimmy Yang <jimmy.yang@oracle.com> Original commit message: Port fix for "bug #54044 Create temporary tables and using innodb crashes" to 5.1 plugin codeline. rb://378, approved by Marko	Jimmy Yang	14 years ago
1819.7.45	Merge Revision revid:jimmy.yang@oracle.com-20100623020431-0r... Merge Revision revid:jimmy.yang@oracle.com-20100623020431-0r2gopb1zlplgu0o from MySQL InnoDB Original revid:jimmy.yang@oracle.com-20100623020431-0r2gopb1zlplgu0o Original Authors: Jimmy Yang <jimmy.yang@oracle.com> Original commit message: Fix bug #54044, Create temporary tables and using innodb crashes. Screen out NULL type columns, and return without creating the table. rb://378 approved by Marko	Jimmy Yang	14 years ago
1819.7.44	merge bug fix for CREATE TABLE with column of type NULL merge bug fix for CREATE TABLE with column of type NULL	Stewart Smith	14 years ago
1819.7.43	merge innobase 1.0.9 build fixes merge innobase 1.0.9 build fixes	Stewart Smith	14 years ago
1819.7.42	fix patch for Fix Bug#54686: 'field->col->mtype == type' ass... fix patch for Fix Bug#54686: 'field->col->mtype == type' assertion error at row/row0sel.c	Stewart Smith	14 years ago

Older »