mariadb/storage/innobase/sync
Sunny Bains 7c6d9a94b7 Bug#54583 InnoDB: Assertion failure sync/sync0sync.c:1226
Silence the UNIV_SYNC_DEBUG assertion failure while upgrading old data files
to multiple rollback segments during server startup. Because the upgrade
takes place while InnoDB is running a single thread, we can safely ignore the
latching order checks without fearing deadlocks.
      
innobase_start_or_create_for_mysql(): Set srv_is_being_started = FALSE
only after trx_sys_create_rsegs() has completed.
      
sync_thread_add_level(): If srv_is_being_started, ignore latching order
violations for SYNC_TRX_SYS_HEADER and SYNC_IBUF_BITMAP.

Create all the non-IO threads after creating the extra rollback segments.

Patch originally from Marko with some additions by Sunny.
2010-07-22 09:16:19 +10:00
..
sync0arr.c Improve InnoDB synchronization primitives on Windows 2010-07-20 15:42:31 -05:00
sync0rw.c Merge a change from mysql-5.1-innodb: 2010-06-01 17:03:55 +03:00
sync0sync.c Bug#54583 InnoDB: Assertion failure sync/sync0sync.c:1226 2010-07-22 09:16:19 +10:00