mirror of
https://github.com/MariaDB/server.git
synced 2025-01-19 13:32:33 +01:00
442ba20a92
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.
|
||
|---|---|---|
| .. | ||
| archive | ||
| blackhole | ||
| csv | ||
| example | ||
| federated | ||
| heap | ||
| ibmdb2i | ||
| innobase | ||
| innodb_plugin | ||
| myisam | ||
| myisammrg | ||
| ndb | ||
| Makefile.am | ||
| mysql_storage_engine.cmake | ||