You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

1005 lines
27 KiB

11 years ago
MDEV-12288 Reset DB_TRX_ID when the history is removed, to speed up MVCC Let InnoDB purge reset DB_TRX_ID,DB_ROLL_PTR when the history is removed. [TODO: It appears that the resetting is not taking place as often as it could be. We should test that a simple INSERT should eventually cause row_purge_reset_trx_id() to be invoked unless DROP TABLE is invoked soon enough.] The InnoDB clustered index record system columns DB_TRX_ID,DB_ROLL_PTR are used by multi-versioning. After the history is no longer needed, these columns can safely be reset to 0 and 1<<55 (to indicate a fresh insert). When a reader sees 0 in the DB_TRX_ID column, it can instantly determine that the record is present the read view. There is no need to acquire the transaction system mutex to check if the transaction exists, because writes can never be conducted by a transaction whose ID is 0. The persistent InnoDB undo log used to be split into two parts: insert_undo and update_undo. The insert_undo log was discarded at transaction commit or rollback, and the update_undo log was processed by the purge subsystem. As part of this change, we will only generate a single undo log for new transactions, and the purge subsystem will reset the DB_TRX_ID whenever a clustered index record is touched. That is, all persistent undo log will be preserved at transaction commit or rollback, to be removed by purge. The InnoDB redo log format is changed in two ways: We remove the redo log record type MLOG_UNDO_HDR_REUSE, and we introduce the MLOG_ZIP_WRITE_TRX_ID record for updating the DB_TRX_ID,DB_ROLL_PTR in a ROW_FORMAT=COMPRESSED table. This is also changing the format of persistent InnoDB data files: undo log and clustered index leaf page records. It will still be possible via import and export to exchange data files with earlier versions of MariaDB. The change to clustered index leaf page records is simple: we allow DB_TRX_ID to be 0. When it comes to the undo log, we must be able to upgrade from earlier MariaDB versions after a clean shutdown (no redo log to apply). While it would be nice to perform a slow shutdown (innodb_fast_shutdown=0) before an upgrade, to empty the undo logs, we cannot assume that this has been done. So, separate insert_undo log may exist for recovered uncommitted transactions. These transactions may be automatically rolled back, or they may be in XA PREPARE state, in which case InnoDB will preserve the transaction until an explicit XA COMMIT or XA ROLLBACK. Upgrade has been tested by starting up MariaDB 10.2 with ./mysql-test-run --manual-gdb innodb.read_only_recovery and then starting up this patched server with and without --innodb-read-only. trx_undo_ptr_t::undo: Renamed from update_undo. trx_undo_ptr_t::old_insert: Renamed from insert_undo. trx_rseg_t::undo_list: Renamed from update_undo_list. trx_rseg_t::undo_cached: Merged from update_undo_cached and insert_undo_cached. trx_rseg_t::old_insert_list: Renamed from insert_undo_list. row_purge_reset_trx_id(): New function to reset the columns. This will be called for all undo processing in purge that does not remove the clustered index record. trx_undo_update_rec_get_update(): Allow trx_id=0 when copying the old DB_TRX_ID of the record to the undo log. ReadView::changes_visible(): Allow id==0. (Return true for it. This is what speeds up the MVCC.) row_vers_impl_x_locked_low(), row_vers_build_for_semi_consistent_read(): Implement a fast path for DB_TRX_ID=0. Always initialize the TRX_UNDO_PAGE_TYPE to 0. Remove undo->type. MLOG_UNDO_HDR_REUSE: Remove. This changes the redo log format! innobase_start_or_create_for_mysql(): Set srv_undo_sources before starting any transactions. The parsing of the MLOG_ZIP_WRITE_TRX_ID record was successfully tested by running the following: ./mtr --parallel=auto --mysqld=--debug=d,ib_log innodb_zip.bug56680 grep MLOG_ZIP_WRITE_TRX_ID var/*/log/mysqld.1.err
8 years ago
MDEV-14477 InnoDB update_time is wrongly updated after partial rollback or internal COMMIT The non-persistent UPDATE_TIME for InnoDB tables was not being updated consistently at transaction commit. If a transaction is partly rolled back so that in the end it will not modify a table that it intended to modify, the update_time will be updated nevertheless. This will also happen when InnoDB fails to write an undo log record for the intended modification. If a transaction is committed internally in InnoDB, instead of being committed from the SQL interface, then the trx_t::mod_tables will not be applied to the update_time of the tables. trx_t::mod_tables: Replace the std::set<dict_table_t*> with std::map<dict_table_t*,undo_no_t>, so that the very first modification within the transaction is identified. trx_undo_report_row_operation(): Update mod_tables for every operation after the undo log record was successfully written. trx_rollback_to_savepoint_low(): After partial rollback, erase from trx_t::mod_tables any tables for which all changes were rolled back. trx_commit_in_memory(): Tighten some assertions and simplify conditions. Invoke trx_update_mod_tables_timestamp() if persistent tables were affected. trx_commit_for_mysql(): Remove the call to trx_update_mod_tables_timestamp(), as it is now invoked at the lower level, in trx_commit_in_memory(). trx_rollback_finish(): Clear mod_tables before invoking trx_commit(), because the trx_commit_in_memory() would otherwise wrongly process mod_tables after a full ROLLBACK.
8 years ago
Remove the flag vers_update_trt THD::vers_update_trt, trx_t::vers_update_trt, trx_savept_t::vers_update_trt: Remove. Instead, determine from trx_t::mod_tables whether versioned columns were affected by the transaction. handlerton::prepare_commit_versioned: Replaces vers_get_trt_data. Return the transaction start ID and also the commit ID, in case the transaction modified any system-versioned columns (0 if not). TR_table::store_data(): Remove (merge with update() below). TR_table::update(): Add the parameters start_id, end_id. ha_commit_trans(): Remove a condition on SQLCOM_ALTER_TABLE. If we need something special for ALTER TABLE...ALGORITHM=INPLACE, that can be done inside InnoDB by modifying trx_t::mod_tables. innodb_prepare_commit_versioned(): Renamed from innodb_get_trt_data(). Check trx_t::mod_tables to see if any changes to versioned columns are present. trx_mod_table_time_t: A pair of logical timestamps, replacing the undo_no_t in trx_mod_tables_t. Keep track of not only the first modification to a persistent table in each transaction, but also the first modification of a versioned column in a table. dtype_t, dict_col_t: Add the accessor is_any_versioned(), to check if the type refers to a system-versioned user or system column. upd_t::affects_versioned(): Check if an update affects a versioned column. trx_undo_report_row_operation(): If a versioned column is affected by the update, invoke trx_mod_table_time_t::set_versioned(). trx_rollback_to_savepoint_low(): If all changes to versioned columns were rolled back, invoke trx_mod_table_time_t::rollback_versioned(), so that trx_mod_table_time_t::is_versioned() will no longer hold.
8 years ago
MDEV-14477 InnoDB update_time is wrongly updated after partial rollback or internal COMMIT The non-persistent UPDATE_TIME for InnoDB tables was not being updated consistently at transaction commit. If a transaction is partly rolled back so that in the end it will not modify a table that it intended to modify, the update_time will be updated nevertheless. This will also happen when InnoDB fails to write an undo log record for the intended modification. If a transaction is committed internally in InnoDB, instead of being committed from the SQL interface, then the trx_t::mod_tables will not be applied to the update_time of the tables. trx_t::mod_tables: Replace the std::set<dict_table_t*> with std::map<dict_table_t*,undo_no_t>, so that the very first modification within the transaction is identified. trx_undo_report_row_operation(): Update mod_tables for every operation after the undo log record was successfully written. trx_rollback_to_savepoint_low(): After partial rollback, erase from trx_t::mod_tables any tables for which all changes were rolled back. trx_commit_in_memory(): Tighten some assertions and simplify conditions. Invoke trx_update_mod_tables_timestamp() if persistent tables were affected. trx_commit_for_mysql(): Remove the call to trx_update_mod_tables_timestamp(), as it is now invoked at the lower level, in trx_commit_in_memory(). trx_rollback_finish(): Clear mod_tables before invoking trx_commit(), because the trx_commit_in_memory() would otherwise wrongly process mod_tables after a full ROLLBACK.
8 years ago
11 years ago
7 years ago
MDEV-12288 Reset DB_TRX_ID when the history is removed, to speed up MVCC Let InnoDB purge reset DB_TRX_ID,DB_ROLL_PTR when the history is removed. [TODO: It appears that the resetting is not taking place as often as it could be. We should test that a simple INSERT should eventually cause row_purge_reset_trx_id() to be invoked unless DROP TABLE is invoked soon enough.] The InnoDB clustered index record system columns DB_TRX_ID,DB_ROLL_PTR are used by multi-versioning. After the history is no longer needed, these columns can safely be reset to 0 and 1<<55 (to indicate a fresh insert). When a reader sees 0 in the DB_TRX_ID column, it can instantly determine that the record is present the read view. There is no need to acquire the transaction system mutex to check if the transaction exists, because writes can never be conducted by a transaction whose ID is 0. The persistent InnoDB undo log used to be split into two parts: insert_undo and update_undo. The insert_undo log was discarded at transaction commit or rollback, and the update_undo log was processed by the purge subsystem. As part of this change, we will only generate a single undo log for new transactions, and the purge subsystem will reset the DB_TRX_ID whenever a clustered index record is touched. That is, all persistent undo log will be preserved at transaction commit or rollback, to be removed by purge. The InnoDB redo log format is changed in two ways: We remove the redo log record type MLOG_UNDO_HDR_REUSE, and we introduce the MLOG_ZIP_WRITE_TRX_ID record for updating the DB_TRX_ID,DB_ROLL_PTR in a ROW_FORMAT=COMPRESSED table. This is also changing the format of persistent InnoDB data files: undo log and clustered index leaf page records. It will still be possible via import and export to exchange data files with earlier versions of MariaDB. The change to clustered index leaf page records is simple: we allow DB_TRX_ID to be 0. When it comes to the undo log, we must be able to upgrade from earlier MariaDB versions after a clean shutdown (no redo log to apply). While it would be nice to perform a slow shutdown (innodb_fast_shutdown=0) before an upgrade, to empty the undo logs, we cannot assume that this has been done. So, separate insert_undo log may exist for recovered uncommitted transactions. These transactions may be automatically rolled back, or they may be in XA PREPARE state, in which case InnoDB will preserve the transaction until an explicit XA COMMIT or XA ROLLBACK. Upgrade has been tested by starting up MariaDB 10.2 with ./mysql-test-run --manual-gdb innodb.read_only_recovery and then starting up this patched server with and without --innodb-read-only. trx_undo_ptr_t::undo: Renamed from update_undo. trx_undo_ptr_t::old_insert: Renamed from insert_undo. trx_rseg_t::undo_list: Renamed from update_undo_list. trx_rseg_t::undo_cached: Merged from update_undo_cached and insert_undo_cached. trx_rseg_t::old_insert_list: Renamed from insert_undo_list. row_purge_reset_trx_id(): New function to reset the columns. This will be called for all undo processing in purge that does not remove the clustered index record. trx_undo_update_rec_get_update(): Allow trx_id=0 when copying the old DB_TRX_ID of the record to the undo log. ReadView::changes_visible(): Allow id==0. (Return true for it. This is what speeds up the MVCC.) row_vers_impl_x_locked_low(), row_vers_build_for_semi_consistent_read(): Implement a fast path for DB_TRX_ID=0. Always initialize the TRX_UNDO_PAGE_TYPE to 0. Remove undo->type. MLOG_UNDO_HDR_REUSE: Remove. This changes the redo log format! innobase_start_or_create_for_mysql(): Set srv_undo_sources before starting any transactions. The parsing of the MLOG_ZIP_WRITE_TRX_ID record was successfully tested by running the following: ./mtr --parallel=auto --mysqld=--debug=d,ib_log innodb_zip.bug56680 grep MLOG_ZIP_WRITE_TRX_ID var/*/log/mysqld.1.err
8 years ago
MDEV-12288 Reset DB_TRX_ID when the history is removed, to speed up MVCC Let InnoDB purge reset DB_TRX_ID,DB_ROLL_PTR when the history is removed. [TODO: It appears that the resetting is not taking place as often as it could be. We should test that a simple INSERT should eventually cause row_purge_reset_trx_id() to be invoked unless DROP TABLE is invoked soon enough.] The InnoDB clustered index record system columns DB_TRX_ID,DB_ROLL_PTR are used by multi-versioning. After the history is no longer needed, these columns can safely be reset to 0 and 1<<55 (to indicate a fresh insert). When a reader sees 0 in the DB_TRX_ID column, it can instantly determine that the record is present the read view. There is no need to acquire the transaction system mutex to check if the transaction exists, because writes can never be conducted by a transaction whose ID is 0. The persistent InnoDB undo log used to be split into two parts: insert_undo and update_undo. The insert_undo log was discarded at transaction commit or rollback, and the update_undo log was processed by the purge subsystem. As part of this change, we will only generate a single undo log for new transactions, and the purge subsystem will reset the DB_TRX_ID whenever a clustered index record is touched. That is, all persistent undo log will be preserved at transaction commit or rollback, to be removed by purge. The InnoDB redo log format is changed in two ways: We remove the redo log record type MLOG_UNDO_HDR_REUSE, and we introduce the MLOG_ZIP_WRITE_TRX_ID record for updating the DB_TRX_ID,DB_ROLL_PTR in a ROW_FORMAT=COMPRESSED table. This is also changing the format of persistent InnoDB data files: undo log and clustered index leaf page records. It will still be possible via import and export to exchange data files with earlier versions of MariaDB. The change to clustered index leaf page records is simple: we allow DB_TRX_ID to be 0. When it comes to the undo log, we must be able to upgrade from earlier MariaDB versions after a clean shutdown (no redo log to apply). While it would be nice to perform a slow shutdown (innodb_fast_shutdown=0) before an upgrade, to empty the undo logs, we cannot assume that this has been done. So, separate insert_undo log may exist for recovered uncommitted transactions. These transactions may be automatically rolled back, or they may be in XA PREPARE state, in which case InnoDB will preserve the transaction until an explicit XA COMMIT or XA ROLLBACK. Upgrade has been tested by starting up MariaDB 10.2 with ./mysql-test-run --manual-gdb innodb.read_only_recovery and then starting up this patched server with and without --innodb-read-only. trx_undo_ptr_t::undo: Renamed from update_undo. trx_undo_ptr_t::old_insert: Renamed from insert_undo. trx_rseg_t::undo_list: Renamed from update_undo_list. trx_rseg_t::undo_cached: Merged from update_undo_cached and insert_undo_cached. trx_rseg_t::old_insert_list: Renamed from insert_undo_list. row_purge_reset_trx_id(): New function to reset the columns. This will be called for all undo processing in purge that does not remove the clustered index record. trx_undo_update_rec_get_update(): Allow trx_id=0 when copying the old DB_TRX_ID of the record to the undo log. ReadView::changes_visible(): Allow id==0. (Return true for it. This is what speeds up the MVCC.) row_vers_impl_x_locked_low(), row_vers_build_for_semi_consistent_read(): Implement a fast path for DB_TRX_ID=0. Always initialize the TRX_UNDO_PAGE_TYPE to 0. Remove undo->type. MLOG_UNDO_HDR_REUSE: Remove. This changes the redo log format! innobase_start_or_create_for_mysql(): Set srv_undo_sources before starting any transactions. The parsing of the MLOG_ZIP_WRITE_TRX_ID record was successfully tested by running the following: ./mtr --parallel=auto --mysqld=--debug=d,ib_log innodb_zip.bug56680 grep MLOG_ZIP_WRITE_TRX_ID var/*/log/mysqld.1.err
8 years ago
MDEV-12288 Reset DB_TRX_ID when the history is removed, to speed up MVCC Let InnoDB purge reset DB_TRX_ID,DB_ROLL_PTR when the history is removed. [TODO: It appears that the resetting is not taking place as often as it could be. We should test that a simple INSERT should eventually cause row_purge_reset_trx_id() to be invoked unless DROP TABLE is invoked soon enough.] The InnoDB clustered index record system columns DB_TRX_ID,DB_ROLL_PTR are used by multi-versioning. After the history is no longer needed, these columns can safely be reset to 0 and 1<<55 (to indicate a fresh insert). When a reader sees 0 in the DB_TRX_ID column, it can instantly determine that the record is present the read view. There is no need to acquire the transaction system mutex to check if the transaction exists, because writes can never be conducted by a transaction whose ID is 0. The persistent InnoDB undo log used to be split into two parts: insert_undo and update_undo. The insert_undo log was discarded at transaction commit or rollback, and the update_undo log was processed by the purge subsystem. As part of this change, we will only generate a single undo log for new transactions, and the purge subsystem will reset the DB_TRX_ID whenever a clustered index record is touched. That is, all persistent undo log will be preserved at transaction commit or rollback, to be removed by purge. The InnoDB redo log format is changed in two ways: We remove the redo log record type MLOG_UNDO_HDR_REUSE, and we introduce the MLOG_ZIP_WRITE_TRX_ID record for updating the DB_TRX_ID,DB_ROLL_PTR in a ROW_FORMAT=COMPRESSED table. This is also changing the format of persistent InnoDB data files: undo log and clustered index leaf page records. It will still be possible via import and export to exchange data files with earlier versions of MariaDB. The change to clustered index leaf page records is simple: we allow DB_TRX_ID to be 0. When it comes to the undo log, we must be able to upgrade from earlier MariaDB versions after a clean shutdown (no redo log to apply). While it would be nice to perform a slow shutdown (innodb_fast_shutdown=0) before an upgrade, to empty the undo logs, we cannot assume that this has been done. So, separate insert_undo log may exist for recovered uncommitted transactions. These transactions may be automatically rolled back, or they may be in XA PREPARE state, in which case InnoDB will preserve the transaction until an explicit XA COMMIT or XA ROLLBACK. Upgrade has been tested by starting up MariaDB 10.2 with ./mysql-test-run --manual-gdb innodb.read_only_recovery and then starting up this patched server with and without --innodb-read-only. trx_undo_ptr_t::undo: Renamed from update_undo. trx_undo_ptr_t::old_insert: Renamed from insert_undo. trx_rseg_t::undo_list: Renamed from update_undo_list. trx_rseg_t::undo_cached: Merged from update_undo_cached and insert_undo_cached. trx_rseg_t::old_insert_list: Renamed from insert_undo_list. row_purge_reset_trx_id(): New function to reset the columns. This will be called for all undo processing in purge that does not remove the clustered index record. trx_undo_update_rec_get_update(): Allow trx_id=0 when copying the old DB_TRX_ID of the record to the undo log. ReadView::changes_visible(): Allow id==0. (Return true for it. This is what speeds up the MVCC.) row_vers_impl_x_locked_low(), row_vers_build_for_semi_consistent_read(): Implement a fast path for DB_TRX_ID=0. Always initialize the TRX_UNDO_PAGE_TYPE to 0. Remove undo->type. MLOG_UNDO_HDR_REUSE: Remove. This changes the redo log format! innobase_start_or_create_for_mysql(): Set srv_undo_sources before starting any transactions. The parsing of the MLOG_ZIP_WRITE_TRX_ID record was successfully tested by running the following: ./mtr --parallel=auto --mysqld=--debug=d,ib_log innodb_zip.bug56680 grep MLOG_ZIP_WRITE_TRX_ID var/*/log/mysqld.1.err
8 years ago
MDEV-12288 Reset DB_TRX_ID when the history is removed, to speed up MVCC Let InnoDB purge reset DB_TRX_ID,DB_ROLL_PTR when the history is removed. [TODO: It appears that the resetting is not taking place as often as it could be. We should test that a simple INSERT should eventually cause row_purge_reset_trx_id() to be invoked unless DROP TABLE is invoked soon enough.] The InnoDB clustered index record system columns DB_TRX_ID,DB_ROLL_PTR are used by multi-versioning. After the history is no longer needed, these columns can safely be reset to 0 and 1<<55 (to indicate a fresh insert). When a reader sees 0 in the DB_TRX_ID column, it can instantly determine that the record is present the read view. There is no need to acquire the transaction system mutex to check if the transaction exists, because writes can never be conducted by a transaction whose ID is 0. The persistent InnoDB undo log used to be split into two parts: insert_undo and update_undo. The insert_undo log was discarded at transaction commit or rollback, and the update_undo log was processed by the purge subsystem. As part of this change, we will only generate a single undo log for new transactions, and the purge subsystem will reset the DB_TRX_ID whenever a clustered index record is touched. That is, all persistent undo log will be preserved at transaction commit or rollback, to be removed by purge. The InnoDB redo log format is changed in two ways: We remove the redo log record type MLOG_UNDO_HDR_REUSE, and we introduce the MLOG_ZIP_WRITE_TRX_ID record for updating the DB_TRX_ID,DB_ROLL_PTR in a ROW_FORMAT=COMPRESSED table. This is also changing the format of persistent InnoDB data files: undo log and clustered index leaf page records. It will still be possible via import and export to exchange data files with earlier versions of MariaDB. The change to clustered index leaf page records is simple: we allow DB_TRX_ID to be 0. When it comes to the undo log, we must be able to upgrade from earlier MariaDB versions after a clean shutdown (no redo log to apply). While it would be nice to perform a slow shutdown (innodb_fast_shutdown=0) before an upgrade, to empty the undo logs, we cannot assume that this has been done. So, separate insert_undo log may exist for recovered uncommitted transactions. These transactions may be automatically rolled back, or they may be in XA PREPARE state, in which case InnoDB will preserve the transaction until an explicit XA COMMIT or XA ROLLBACK. Upgrade has been tested by starting up MariaDB 10.2 with ./mysql-test-run --manual-gdb innodb.read_only_recovery and then starting up this patched server with and without --innodb-read-only. trx_undo_ptr_t::undo: Renamed from update_undo. trx_undo_ptr_t::old_insert: Renamed from insert_undo. trx_rseg_t::undo_list: Renamed from update_undo_list. trx_rseg_t::undo_cached: Merged from update_undo_cached and insert_undo_cached. trx_rseg_t::old_insert_list: Renamed from insert_undo_list. row_purge_reset_trx_id(): New function to reset the columns. This will be called for all undo processing in purge that does not remove the clustered index record. trx_undo_update_rec_get_update(): Allow trx_id=0 when copying the old DB_TRX_ID of the record to the undo log. ReadView::changes_visible(): Allow id==0. (Return true for it. This is what speeds up the MVCC.) row_vers_impl_x_locked_low(), row_vers_build_for_semi_consistent_read(): Implement a fast path for DB_TRX_ID=0. Always initialize the TRX_UNDO_PAGE_TYPE to 0. Remove undo->type. MLOG_UNDO_HDR_REUSE: Remove. This changes the redo log format! innobase_start_or_create_for_mysql(): Set srv_undo_sources before starting any transactions. The parsing of the MLOG_ZIP_WRITE_TRX_ID record was successfully tested by running the following: ./mtr --parallel=auto --mysqld=--debug=d,ib_log innodb_zip.bug56680 grep MLOG_ZIP_WRITE_TRX_ID var/*/log/mysqld.1.err
8 years ago
9 years ago
7 years ago
11 years ago
MDEV-11369 Instant ADD COLUMN for InnoDB For InnoDB tables, adding, dropping and reordering columns has required a rebuild of the table and all its indexes. Since MySQL 5.6 (and MariaDB 10.0) this has been supported online (LOCK=NONE), allowing concurrent modification of the tables. This work revises the InnoDB ROW_FORMAT=REDUNDANT, ROW_FORMAT=COMPACT and ROW_FORMAT=DYNAMIC so that columns can be appended instantaneously, with only minor changes performed to the table structure. The counter innodb_instant_alter_column in INFORMATION_SCHEMA.GLOBAL_STATUS is incremented whenever a table rebuild operation is converted into an instant ADD COLUMN operation. ROW_FORMAT=COMPRESSED tables will not support instant ADD COLUMN. Some usability limitations will be addressed in subsequent work: MDEV-13134 Introduce ALTER TABLE attributes ALGORITHM=NOCOPY and ALGORITHM=INSTANT MDEV-14016 Allow instant ADD COLUMN, ADD INDEX, LOCK=NONE The format of the clustered index (PRIMARY KEY) is changed as follows: (1) The FIL_PAGE_TYPE of the root page will be FIL_PAGE_TYPE_INSTANT, and a new field PAGE_INSTANT will contain the original number of fields in the clustered index ('core' fields). If instant ADD COLUMN has not been used or the table becomes empty, or the very first instant ADD COLUMN operation is rolled back, the fields PAGE_INSTANT and FIL_PAGE_TYPE will be reset to 0 and FIL_PAGE_INDEX. (2) A special 'default row' record is inserted into the leftmost leaf, between the page infimum and the first user record. This record is distinguished by the REC_INFO_MIN_REC_FLAG, and it is otherwise in the same format as records that contain values for the instantly added columns. This 'default row' always has the same number of fields as the clustered index according to the table definition. The values of 'core' fields are to be ignored. For other fields, the 'default row' will contain the default values as they were during the ALTER TABLE statement. (If the column default values are changed later, those values will only be stored in the .frm file. The 'default row' will contain the original evaluated values, which must be the same for every row.) The 'default row' must be completely hidden from higher-level access routines. Assertions have been added to ensure that no 'default row' is ever present in the adaptive hash index or in locked records. The 'default row' is never delete-marked. (3) In clustered index leaf page records, the number of fields must reside between the number of 'core' fields (dict_index_t::n_core_fields introduced in this work) and dict_index_t::n_fields. If the number of fields is less than dict_index_t::n_fields, the missing fields are replaced with the column value of the 'default row'. Note: The number of fields in the record may shrink if some of the last instantly added columns are updated to the value that is in the 'default row'. The function btr_cur_trim() implements this 'compression' on update and rollback; dtuple::trim() implements it on insert. (4) In ROW_FORMAT=COMPACT and ROW_FORMAT=DYNAMIC records, the new status value REC_STATUS_COLUMNS_ADDED will indicate the presence of a new record header that will encode n_fields-n_core_fields-1 in 1 or 2 bytes. (In ROW_FORMAT=REDUNDANT records, the record header always explicitly encodes the number of fields.) We introduce the undo log record type TRX_UNDO_INSERT_DEFAULT for covering the insert of the 'default row' record when instant ADD COLUMN is used for the first time. Subsequent instant ADD COLUMN can use TRX_UNDO_UPD_EXIST_REC. This is joint work with Vin Chen (陈福荣) from Tencent. The design that was discussed in April 2017 would not have allowed import or export of data files, because instead of the 'default row' it would have introduced a data dictionary table. The test rpl.rpl_alter_instant is exactly as contributed in pull request #408. The test innodb.instant_alter is based on a contributed test. The redo log record format changes for ROW_FORMAT=DYNAMIC and ROW_FORMAT=COMPACT are as contributed. (With this change present, crash recovery from MariaDB 10.3.1 will fail in spectacular ways!) Also the semantics of higher-level redo log records that modify the PAGE_INSTANT field is changed. The redo log format version identifier was already changed to LOG_HEADER_FORMAT_CURRENT=103 in MariaDB 10.3.1. Everything else has been rewritten by me. Thanks to Elena Stepanova, the code has been tested extensively. When rolling back an instant ADD COLUMN operation, we must empty the PAGE_FREE list after deleting or shortening the 'default row' record, by calling either btr_page_empty() or btr_page_reorganize(). We must know the size of each entry in the PAGE_FREE list. If rollback left a freed copy of the 'default row' in the PAGE_FREE list, we would be unable to determine its size (if it is in ROW_FORMAT=COMPACT or ROW_FORMAT=DYNAMIC) because it would contain more fields than the rolled-back definition of the clustered index. UNIV_SQL_DEFAULT: A new special constant that designates an instantly added column that is not present in the clustered index record. len_is_stored(): Check if a length is an actual length. There are two magic length values: UNIV_SQL_DEFAULT, UNIV_SQL_NULL. dict_col_t::def_val: The 'default row' value of the column. If the column is not added instantly, def_val.len will be UNIV_SQL_DEFAULT. dict_col_t: Add the accessors is_virtual(), is_nullable(), is_instant(), instant_value(). dict_col_t::remove_instant(): Remove the 'instant ADD' status of a column. dict_col_t::name(const dict_table_t& table): Replaces dict_table_get_col_name(). dict_index_t::n_core_fields: The original number of fields. For secondary indexes and if instant ADD COLUMN has not been used, this will be equal to dict_index_t::n_fields. dict_index_t::n_core_null_bytes: Number of bytes needed to represent the null flags; usually equal to UT_BITS_IN_BYTES(n_nullable). dict_index_t::NO_CORE_NULL_BYTES: Magic value signalling that n_core_null_bytes was not initialized yet from the clustered index root page. dict_index_t: Add the accessors is_instant(), is_clust(), get_n_nullable(), instant_field_value(). dict_index_t::instant_add_field(): Adjust clustered index metadata for instant ADD COLUMN. dict_index_t::remove_instant(): Remove the 'instant ADD' status of a clustered index when the table becomes empty, or the very first instant ADD COLUMN operation is rolled back. dict_table_t: Add the accessors is_instant(), is_temporary(), supports_instant(). dict_table_t::instant_add_column(): Adjust metadata for instant ADD COLUMN. dict_table_t::rollback_instant(): Adjust metadata on the rollback of instant ADD COLUMN. prepare_inplace_alter_table_dict(): First create the ctx->new_table, and only then decide if the table really needs to be rebuilt. We must split the creation of table or index metadata from the creation of the dictionary table records and the creation of the data. In this way, we can transform a table-rebuilding operation into an instant ADD COLUMN operation. Dictionary objects will only be added to cache when table rebuilding or index creation is needed. The ctx->instant_table will never be added to cache. dict_table_t::add_to_cache(): Modified and renamed from dict_table_add_to_cache(). Do not modify the table metadata. Let the callers invoke dict_table_add_system_columns() and if needed, set can_be_evicted. dict_create_sys_tables_tuple(), dict_create_table_step(): Omit the system columns (which will now exist in the dict_table_t object already at this point). dict_create_table_step(): Expect the callers to invoke dict_table_add_system_columns(). pars_create_table(): Before creating the table creation execution graph, invoke dict_table_add_system_columns(). row_create_table_for_mysql(): Expect all callers to invoke dict_table_add_system_columns(). create_index_dict(): Replaces row_merge_create_index_graph(). innodb_update_n_cols(): Renamed from innobase_update_n_virtual(). Call my_error() if an error occurs. btr_cur_instant_init(), btr_cur_instant_init_low(), btr_cur_instant_root_init(): Load additional metadata from the clustered index and set dict_index_t::n_core_null_bytes. This is invoked when table metadata is first loaded into the data dictionary. dict_boot(): Initialize n_core_null_bytes for the four hard-coded dictionary tables. dict_create_index_step(): Initialize n_core_null_bytes. This is executed as part of CREATE TABLE. dict_index_build_internal_clust(): Initialize n_core_null_bytes to NO_CORE_NULL_BYTES if table->supports_instant(). row_create_index_for_mysql(): Initialize n_core_null_bytes for CREATE TEMPORARY TABLE. commit_cache_norebuild(): Call the code to rename or enlarge columns in the cache only if instant ADD COLUMN is not being used. (Instant ADD COLUMN would copy all column metadata from instant_table to old_table, including the names and lengths.) PAGE_INSTANT: A new 13-bit field for storing dict_index_t::n_core_fields. This is repurposing the 16-bit field PAGE_DIRECTION, of which only the least significant 3 bits were used. The original byte containing PAGE_DIRECTION will be accessible via the new constant PAGE_DIRECTION_B. page_get_instant(), page_set_instant(): Accessors for the PAGE_INSTANT. page_ptr_get_direction(), page_get_direction(), page_ptr_set_direction(): Accessors for PAGE_DIRECTION. page_direction_reset(): Reset PAGE_DIRECTION, PAGE_N_DIRECTION. page_direction_increment(): Increment PAGE_N_DIRECTION and set PAGE_DIRECTION. rec_get_offsets(): Use the 'leaf' parameter for non-debug purposes, and assume that heap_no is always set. Initialize all dict_index_t::n_fields for ROW_FORMAT=REDUNDANT records, even if the record contains fewer fields. rec_offs_make_valid(): Add the parameter 'leaf'. rec_copy_prefix_to_dtuple(): Assert that the tuple is only built on the core fields. Instant ADD COLUMN only applies to the clustered index, and we should never build a search key that has more than the PRIMARY KEY and possibly DB_TRX_ID,DB_ROLL_PTR. All these columns are always present. dict_index_build_data_tuple(): Remove assertions that would be duplicated in rec_copy_prefix_to_dtuple(). rec_init_offsets(): Support ROW_FORMAT=REDUNDANT records whose number of fields is between n_core_fields and n_fields. cmp_rec_rec_with_match(): Implement the comparison between two MIN_REC_FLAG records. trx_t::in_rollback: Make the field available in non-debug builds. trx_start_for_ddl_low(): Remove dangerous error-tolerance. A dictionary transaction must be flagged as such before it has generated any undo log records. This is because trx_undo_assign_undo() will mark the transaction as a dictionary transaction in the undo log header right before the very first undo log record is being written. btr_index_rec_validate(): Account for instant ADD COLUMN row_undo_ins_remove_clust_rec(): On the rollback of an insert into SYS_COLUMNS, revert instant ADD COLUMN in the cache by removing the last column from the table and the clustered index. row_search_on_row_ref(), row_undo_mod_parse_undo_rec(), row_undo_mod(), trx_undo_update_rec_get_update(): Handle the 'default row' as a special case. dtuple_t::trim(index): Omit a redundant suffix of an index tuple right before insert or update. After instant ADD COLUMN, if the last fields of a clustered index tuple match the 'default row', there is no need to store them. While trimming the entry, we must hold a page latch, so that the table cannot be emptied and the 'default row' be deleted. btr_cur_optimistic_update(), btr_cur_pessimistic_update(), row_upd_clust_rec_by_insert(), row_ins_clust_index_entry_low(): Invoke dtuple_t::trim() if needed. row_ins_clust_index_entry(): Restore dtuple_t::n_fields after calling row_ins_clust_index_entry_low(). rec_get_converted_size(), rec_get_converted_size_comp(): Allow the number of fields to be between n_core_fields and n_fields. Do not support infimum,supremum. They are never supposed to be stored in dtuple_t, because page creation nowadays uses a lower-level method for initializing them. rec_convert_dtuple_to_rec_comp(): Assign the status bits based on the number of fields. btr_cur_trim(): In an update, trim the index entry as needed. For the 'default row', handle rollback specially. For user records, omit fields that match the 'default row'. btr_cur_optimistic_delete_func(), btr_cur_pessimistic_delete(): Skip locking and adaptive hash index for the 'default row'. row_log_table_apply_convert_mrec(): Replace 'default row' values if needed. In the temporary file that is applied by row_log_table_apply(), we must identify whether the records contain the extra header for instantly added columns. For now, we will allocate an additional byte for this for ROW_T_INSERT and ROW_T_UPDATE records when the source table has been subject to instant ADD COLUMN. The ROW_T_DELETE records are fine, as they will be converted and will only contain 'core' columns (PRIMARY KEY and some system columns) that are converted from dtuple_t. rec_get_converted_size_temp(), rec_init_offsets_temp(), rec_convert_dtuple_to_temp(): Add the parameter 'status'. REC_INFO_DEFAULT_ROW = REC_INFO_MIN_REC_FLAG | REC_STATUS_COLUMNS_ADDED: An info_bits constant for distinguishing the 'default row' record. rec_comp_status_t: An enum of the status bit values. rec_leaf_format: An enum that replaces the bool parameter of rec_init_offsets_comp_ordinary().
8 years ago
  1. /*****************************************************************************
  2. Copyright (c) 1996, 2017, Oracle and/or its affiliates. All Rights Reserved.
  3. Copyright (c) 2016, 2019, MariaDB Corporation.
  4. This program is free software; you can redistribute it and/or modify it under
  5. the terms of the GNU General Public License as published by the Free Software
  6. Foundation; version 2 of the License.
  7. This program is distributed in the hope that it will be useful, but WITHOUT
  8. ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
  9. FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
  10. You should have received a copy of the GNU General Public License along with
  11. this program; if not, write to the Free Software Foundation, Inc.,
  12. 51 Franklin Street, Fifth Floor, Boston, MA 02110-1335 USA
  13. *****************************************************************************/
  14. /**************************************************//**
  15. @file trx/trx0roll.cc
  16. Transaction rollback
  17. Created 3/26/1996 Heikki Tuuri
  18. *******************************************************/
  19. #include "trx0roll.h"
  20. #include <my_service_manager.h>
  21. #include <mysql/service_wsrep.h>
  22. #include "fsp0fsp.h"
  23. #include "lock0lock.h"
  24. #include "mach0data.h"
  25. #include "pars0pars.h"
  26. #include "que0que.h"
  27. #include "row0mysql.h"
  28. #include "row0undo.h"
  29. #include "srv0mon.h"
  30. #include "srv0start.h"
  31. #include "trx0rec.h"
  32. #include "trx0rseg.h"
  33. #include "trx0sys.h"
  34. #include "trx0trx.h"
  35. #include "trx0undo.h"
  36. /** true if trx_rollback_all_recovered() thread is active */
  37. bool trx_rollback_is_active;
  38. /** In crash recovery, the current trx to be rolled back; NULL otherwise */
  39. const trx_t* trx_roll_crash_recv_trx;
  40. /** Finish transaction rollback.
  41. @param[in,out] trx transaction
  42. @return whether the rollback was completed normally
  43. @retval false if the rollback was aborted by shutdown */
  44. static bool trx_rollback_finish(trx_t* trx)
  45. {
  46. trx->mod_tables.clear();
  47. bool finished = trx->error_state == DB_SUCCESS;
  48. if (UNIV_LIKELY(finished)) {
  49. trx_commit(trx);
  50. } else {
  51. ut_a(trx->error_state == DB_INTERRUPTED);
  52. ut_ad(!srv_is_being_started);
  53. ut_a(!srv_undo_sources);
  54. ut_ad(srv_fast_shutdown);
  55. ut_d(trx->in_rollback = false);
  56. if (trx_undo_t*& undo = trx->rsegs.m_redo.old_insert) {
  57. UT_LIST_REMOVE(trx->rsegs.m_redo.rseg->old_insert_list,
  58. undo);
  59. ut_free(undo);
  60. undo = NULL;
  61. }
  62. if (trx_undo_t*& undo = trx->rsegs.m_redo.undo) {
  63. UT_LIST_REMOVE(trx->rsegs.m_redo.rseg->undo_list,
  64. undo);
  65. ut_free(undo);
  66. undo = NULL;
  67. }
  68. if (trx_undo_t*& undo = trx->rsegs.m_noredo.undo) {
  69. UT_LIST_REMOVE(trx->rsegs.m_noredo.rseg->undo_list,
  70. undo);
  71. ut_free(undo);
  72. undo = NULL;
  73. }
  74. trx_commit_low(trx, NULL);
  75. }
  76. trx->lock.que_state = TRX_QUE_RUNNING;
  77. return finished;
  78. }
  79. /*******************************************************************//**
  80. Rollback a transaction used in MySQL. */
  81. static
  82. void
  83. trx_rollback_to_savepoint_low(
  84. /*==========================*/
  85. trx_t* trx, /*!< in: transaction handle */
  86. trx_savept_t* savept) /*!< in: pointer to savepoint undo number, if
  87. partial rollback requested, or NULL for
  88. complete rollback */
  89. {
  90. que_thr_t* thr;
  91. mem_heap_t* heap;
  92. roll_node_t* roll_node;
  93. heap = mem_heap_create(512);
  94. roll_node = roll_node_create(heap);
  95. if (savept != NULL) {
  96. roll_node->savept = savept;
  97. check_trx_state(trx);
  98. } else {
  99. assert_trx_nonlocking_or_in_list(trx);
  100. }
  101. trx->error_state = DB_SUCCESS;
  102. if (trx->has_logged_or_recovered()) {
  103. ut_ad(trx->rsegs.m_redo.rseg != 0
  104. || trx->rsegs.m_noredo.rseg != 0);
  105. thr = pars_complete_graph_for_exec(roll_node, trx, heap, NULL);
  106. ut_a(thr == que_fork_start_command(
  107. static_cast<que_fork_t*>(que_node_get_parent(thr))));
  108. que_run_threads(thr);
  109. ut_a(roll_node->undo_thr != NULL);
  110. que_run_threads(roll_node->undo_thr);
  111. /* Free the memory reserved by the undo graph. */
  112. que_graph_free(static_cast<que_t*>(
  113. roll_node->undo_thr->common.parent));
  114. }
  115. if (savept == NULL) {
  116. trx_rollback_finish(trx);
  117. MONITOR_INC(MONITOR_TRX_ROLLBACK);
  118. } else {
  119. ut_a(trx->error_state == DB_SUCCESS);
  120. const undo_no_t limit = savept->least_undo_no;
  121. for (trx_mod_tables_t::iterator i = trx->mod_tables.begin();
  122. i != trx->mod_tables.end(); ) {
  123. trx_mod_tables_t::iterator j = i++;
  124. ut_ad(j->second.valid());
  125. if (j->second.rollback(limit)) {
  126. trx->mod_tables.erase(j);
  127. }
  128. }
  129. trx->lock.que_state = TRX_QUE_RUNNING;
  130. MONITOR_INC(MONITOR_TRX_ROLLBACK_SAVEPOINT);
  131. }
  132. mem_heap_free(heap);
  133. /* There might be work for utility threads.*/
  134. srv_active_wake_master_thread();
  135. MONITOR_DEC(MONITOR_TRX_ACTIVE);
  136. }
  137. /*******************************************************************//**
  138. Rollback a transaction to a given savepoint or do a complete rollback.
  139. @return error code or DB_SUCCESS */
  140. dberr_t
  141. trx_rollback_to_savepoint(
  142. /*======================*/
  143. trx_t* trx, /*!< in: transaction handle */
  144. trx_savept_t* savept) /*!< in: pointer to savepoint undo number, if
  145. partial rollback requested, or NULL for
  146. complete rollback */
  147. {
  148. #ifdef WITH_WSREP
  149. if (savept == NULL && wsrep_on(trx->mysql_thd)) {
  150. wsrep_handle_SR_rollback(NULL, trx->mysql_thd);
  151. }
  152. #endif /* WITH_WSREP */
  153. ut_ad(!trx_mutex_own(trx));
  154. trx_start_if_not_started_xa(trx, true);
  155. trx_rollback_to_savepoint_low(trx, savept);
  156. return(trx->error_state);
  157. }
  158. /*******************************************************************//**
  159. Rollback a transaction used in MySQL.
  160. @return error code or DB_SUCCESS */
  161. static
  162. dberr_t
  163. trx_rollback_for_mysql_low(
  164. /*=======================*/
  165. trx_t* trx) /*!< in/out: transaction */
  166. {
  167. trx->op_info = "rollback";
  168. /* If we are doing the XA recovery of prepared transactions,
  169. then the transaction object does not have an InnoDB session
  170. object, and we set a dummy session that we use for all MySQL
  171. transactions. */
  172. trx_rollback_to_savepoint_low(trx, NULL);
  173. trx->op_info = "";
  174. return(trx->error_state);
  175. }
  176. /** Rollback a transaction used in MySQL
  177. @param[in, out] trx transaction
  178. @return error code or DB_SUCCESS */
  179. dberr_t trx_rollback_for_mysql(trx_t* trx)
  180. {
  181. /* We are reading trx->state without holding trx_sys.mutex
  182. here, because the rollback should be invoked for a running
  183. active MySQL transaction (or recovered prepared transaction)
  184. that is associated with the current thread. */
  185. switch (trx->state) {
  186. case TRX_STATE_NOT_STARTED:
  187. trx->will_lock = 0;
  188. ut_ad(trx->mysql_thd);
  189. return(DB_SUCCESS);
  190. case TRX_STATE_ACTIVE:
  191. ut_ad(trx->mysql_thd);
  192. assert_trx_nonlocking_or_in_list(trx);
  193. return(trx_rollback_for_mysql_low(trx));
  194. case TRX_STATE_PREPARED:
  195. case TRX_STATE_PREPARED_RECOVERED:
  196. ut_ad(!trx_is_autocommit_non_locking(trx));
  197. if (trx->rsegs.m_redo.undo || trx->rsegs.m_redo.old_insert) {
  198. /* Change the undo log state back from
  199. TRX_UNDO_PREPARED to TRX_UNDO_ACTIVE
  200. so that if the system gets killed,
  201. recovery will perform the rollback. */
  202. ut_ad(!trx->rsegs.m_redo.undo
  203. || trx->rsegs.m_redo.undo->rseg
  204. == trx->rsegs.m_redo.rseg);
  205. ut_ad(!trx->rsegs.m_redo.old_insert
  206. || trx->rsegs.m_redo.old_insert->rseg
  207. == trx->rsegs.m_redo.rseg);
  208. mtr_t mtr;
  209. mtr.start();
  210. mutex_enter(&trx->rsegs.m_redo.rseg->mutex);
  211. if (trx_undo_t* undo = trx->rsegs.m_redo.undo) {
  212. trx_undo_set_state_at_prepare(trx, undo, true,
  213. &mtr);
  214. }
  215. if (trx_undo_t* undo = trx->rsegs.m_redo.old_insert) {
  216. trx_undo_set_state_at_prepare(trx, undo, true,
  217. &mtr);
  218. }
  219. mutex_exit(&trx->rsegs.m_redo.rseg->mutex);
  220. /* Persist the XA ROLLBACK, so that crash
  221. recovery will replay the rollback in case
  222. the redo log gets applied past this point. */
  223. mtr.commit();
  224. ut_ad(mtr.commit_lsn() > 0);
  225. }
  226. #ifdef ENABLED_DEBUG_SYNC
  227. if (trx->mysql_thd == NULL) {
  228. /* We could be executing XA ROLLBACK after
  229. XA PREPARE and a server restart. */
  230. } else if (!trx->has_logged_persistent()) {
  231. /* innobase_close_connection() may roll back a
  232. transaction that did not generate any
  233. persistent undo log. The DEBUG_SYNC
  234. would cause an assertion failure for a
  235. disconnected thread.
  236. NOTE: InnoDB will not know about the XID
  237. if no persistent undo log was generated. */
  238. } else {
  239. DEBUG_SYNC_C("trx_xa_rollback");
  240. }
  241. #endif /* ENABLED_DEBUG_SYNC */
  242. return(trx_rollback_for_mysql_low(trx));
  243. case TRX_STATE_COMMITTED_IN_MEMORY:
  244. check_trx_state(trx);
  245. break;
  246. }
  247. ut_error;
  248. return(DB_CORRUPTION);
  249. }
  250. /*******************************************************************//**
  251. Rollback the latest SQL statement for MySQL.
  252. @return error code or DB_SUCCESS */
  253. dberr_t
  254. trx_rollback_last_sql_stat_for_mysql(
  255. /*=================================*/
  256. trx_t* trx) /*!< in/out: transaction */
  257. {
  258. dberr_t err;
  259. /* We are reading trx->state without holding trx_sys.mutex
  260. here, because the statement rollback should be invoked for a
  261. running active MySQL transaction that is associated with the
  262. current thread. */
  263. ut_ad(trx->mysql_thd);
  264. switch (trx->state) {
  265. case TRX_STATE_NOT_STARTED:
  266. return(DB_SUCCESS);
  267. case TRX_STATE_ACTIVE:
  268. assert_trx_nonlocking_or_in_list(trx);
  269. trx->op_info = "rollback of SQL statement";
  270. err = trx_rollback_to_savepoint(
  271. trx, &trx->last_sql_stat_start);
  272. if (trx->fts_trx != NULL) {
  273. fts_savepoint_rollback_last_stmt(trx);
  274. }
  275. /* The following call should not be needed,
  276. but we play it safe: */
  277. trx_mark_sql_stat_end(trx);
  278. trx->op_info = "";
  279. return(err);
  280. case TRX_STATE_PREPARED:
  281. case TRX_STATE_PREPARED_RECOVERED:
  282. case TRX_STATE_COMMITTED_IN_MEMORY:
  283. /* The statement rollback is only allowed on an ACTIVE
  284. transaction, not a PREPARED or COMMITTED one. */
  285. break;
  286. }
  287. ut_error;
  288. return(DB_CORRUPTION);
  289. }
  290. /*******************************************************************//**
  291. Search for a savepoint using name.
  292. @return savepoint if found else NULL */
  293. static
  294. trx_named_savept_t*
  295. trx_savepoint_find(
  296. /*===============*/
  297. trx_t* trx, /*!< in: transaction */
  298. const char* name) /*!< in: savepoint name */
  299. {
  300. trx_named_savept_t* savep;
  301. for (savep = UT_LIST_GET_FIRST(trx->trx_savepoints);
  302. savep != NULL;
  303. savep = UT_LIST_GET_NEXT(trx_savepoints, savep)) {
  304. if (0 == ut_strcmp(savep->name, name)) {
  305. return(savep);
  306. }
  307. }
  308. return(NULL);
  309. }
  310. /*******************************************************************//**
  311. Frees a single savepoint struct. */
  312. static
  313. void
  314. trx_roll_savepoint_free(
  315. /*=====================*/
  316. trx_t* trx, /*!< in: transaction handle */
  317. trx_named_savept_t* savep) /*!< in: savepoint to free */
  318. {
  319. UT_LIST_REMOVE(trx->trx_savepoints, savep);
  320. ut_free(savep->name);
  321. ut_free(savep);
  322. }
  323. /*******************************************************************//**
  324. Frees savepoint structs starting from savep. */
  325. void
  326. trx_roll_savepoints_free(
  327. /*=====================*/
  328. trx_t* trx, /*!< in: transaction handle */
  329. trx_named_savept_t* savep) /*!< in: free all savepoints starting
  330. with this savepoint i*/
  331. {
  332. while (savep != NULL) {
  333. trx_named_savept_t* next_savep;
  334. next_savep = UT_LIST_GET_NEXT(trx_savepoints, savep);
  335. trx_roll_savepoint_free(trx, savep);
  336. savep = next_savep;
  337. }
  338. }
  339. /*******************************************************************//**
  340. Rolls back a transaction back to a named savepoint. Modifications after the
  341. savepoint are undone but InnoDB does NOT release the corresponding locks
  342. which are stored in memory. If a lock is 'implicit', that is, a new inserted
  343. row holds a lock where the lock information is carried by the trx id stored in
  344. the row, these locks are naturally released in the rollback. Savepoints which
  345. were set after this savepoint are deleted.
  346. @return if no savepoint of the name found then DB_NO_SAVEPOINT,
  347. otherwise DB_SUCCESS */
  348. static MY_ATTRIBUTE((nonnull, warn_unused_result))
  349. dberr_t
  350. trx_rollback_to_savepoint_for_mysql_low(
  351. /*====================================*/
  352. trx_t* trx, /*!< in/out: transaction */
  353. trx_named_savept_t* savep, /*!< in/out: savepoint */
  354. int64_t* mysql_binlog_cache_pos)
  355. /*!< out: the MySQL binlog
  356. cache position corresponding
  357. to this savepoint; MySQL needs
  358. this information to remove the
  359. binlog entries of the queries
  360. executed after the savepoint */
  361. {
  362. dberr_t err;
  363. ut_ad(trx_state_eq(trx, TRX_STATE_ACTIVE));
  364. ut_ad(trx->mysql_thd);
  365. /* Free all savepoints strictly later than savep. */
  366. trx_roll_savepoints_free(
  367. trx, UT_LIST_GET_NEXT(trx_savepoints, savep));
  368. *mysql_binlog_cache_pos = savep->mysql_binlog_cache_pos;
  369. trx->op_info = "rollback to a savepoint";
  370. err = trx_rollback_to_savepoint(trx, &savep->savept);
  371. /* Store the current undo_no of the transaction so that
  372. we know where to roll back if we have to roll back the
  373. next SQL statement: */
  374. trx_mark_sql_stat_end(trx);
  375. trx->op_info = "";
  376. #ifdef WITH_WSREP
  377. trx->lock.was_chosen_as_wsrep_victim = FALSE;
  378. #endif
  379. return(err);
  380. }
  381. /*******************************************************************//**
  382. Rolls back a transaction back to a named savepoint. Modifications after the
  383. savepoint are undone but InnoDB does NOT release the corresponding locks
  384. which are stored in memory. If a lock is 'implicit', that is, a new inserted
  385. row holds a lock where the lock information is carried by the trx id stored in
  386. the row, these locks are naturally released in the rollback. Savepoints which
  387. were set after this savepoint are deleted.
  388. @return if no savepoint of the name found then DB_NO_SAVEPOINT,
  389. otherwise DB_SUCCESS */
  390. dberr_t
  391. trx_rollback_to_savepoint_for_mysql(
  392. /*================================*/
  393. trx_t* trx, /*!< in: transaction handle */
  394. const char* savepoint_name, /*!< in: savepoint name */
  395. int64_t* mysql_binlog_cache_pos) /*!< out: the MySQL binlog cache
  396. position corresponding to this
  397. savepoint; MySQL needs this
  398. information to remove the
  399. binlog entries of the queries
  400. executed after the savepoint */
  401. {
  402. trx_named_savept_t* savep;
  403. /* We are reading trx->state without holding trx_sys.mutex
  404. here, because the savepoint rollback should be invoked for a
  405. running active MySQL transaction that is associated with the
  406. current thread. */
  407. ut_ad(trx->mysql_thd);
  408. savep = trx_savepoint_find(trx, savepoint_name);
  409. if (savep == NULL) {
  410. return(DB_NO_SAVEPOINT);
  411. }
  412. switch (trx->state) {
  413. case TRX_STATE_NOT_STARTED:
  414. ib::error() << "Transaction has a savepoint "
  415. << savep->name
  416. << " though it is not started";
  417. return(DB_ERROR);
  418. case TRX_STATE_ACTIVE:
  419. return(trx_rollback_to_savepoint_for_mysql_low(
  420. trx, savep, mysql_binlog_cache_pos));
  421. case TRX_STATE_PREPARED:
  422. case TRX_STATE_PREPARED_RECOVERED:
  423. case TRX_STATE_COMMITTED_IN_MEMORY:
  424. /* The savepoint rollback is only allowed on an ACTIVE
  425. transaction, not a PREPARED or COMMITTED one. */
  426. break;
  427. }
  428. ut_error;
  429. return(DB_CORRUPTION);
  430. }
  431. /*******************************************************************//**
  432. Creates a named savepoint. If the transaction is not yet started, starts it.
  433. If there is already a savepoint of the same name, this call erases that old
  434. savepoint and replaces it with a new. Savepoints are deleted in a transaction
  435. commit or rollback.
  436. @return always DB_SUCCESS */
  437. dberr_t
  438. trx_savepoint_for_mysql(
  439. /*====================*/
  440. trx_t* trx, /*!< in: transaction handle */
  441. const char* savepoint_name, /*!< in: savepoint name */
  442. int64_t binlog_cache_pos) /*!< in: MySQL binlog cache
  443. position corresponding to this
  444. connection at the time of the
  445. savepoint */
  446. {
  447. trx_named_savept_t* savep;
  448. trx_start_if_not_started_xa(trx, false);
  449. savep = trx_savepoint_find(trx, savepoint_name);
  450. if (savep) {
  451. /* There is a savepoint with the same name: free that */
  452. UT_LIST_REMOVE(trx->trx_savepoints, savep);
  453. ut_free(savep->name);
  454. ut_free(savep);
  455. }
  456. /* Create a new savepoint and add it as the last in the list */
  457. savep = static_cast<trx_named_savept_t*>(
  458. ut_malloc_nokey(sizeof(*savep)));
  459. savep->name = mem_strdup(savepoint_name);
  460. savep->savept = trx_savept_take(trx);
  461. savep->mysql_binlog_cache_pos = binlog_cache_pos;
  462. UT_LIST_ADD_LAST(trx->trx_savepoints, savep);
  463. return(DB_SUCCESS);
  464. }
  465. /*******************************************************************//**
  466. Releases only the named savepoint. Savepoints which were set after this
  467. savepoint are left as is.
  468. @return if no savepoint of the name found then DB_NO_SAVEPOINT,
  469. otherwise DB_SUCCESS */
  470. dberr_t
  471. trx_release_savepoint_for_mysql(
  472. /*============================*/
  473. trx_t* trx, /*!< in: transaction handle */
  474. const char* savepoint_name) /*!< in: savepoint name */
  475. {
  476. trx_named_savept_t* savep;
  477. ut_ad(trx_state_eq(trx, TRX_STATE_ACTIVE, true)
  478. || trx_state_eq(trx, TRX_STATE_PREPARED, true));
  479. ut_ad(trx->mysql_thd);
  480. savep = trx_savepoint_find(trx, savepoint_name);
  481. if (savep != NULL) {
  482. trx_roll_savepoint_free(trx, savep);
  483. }
  484. return(savep != NULL ? DB_SUCCESS : DB_NO_SAVEPOINT);
  485. }
  486. /*******************************************************************//**
  487. Determines if this transaction is rolling back an incomplete transaction
  488. in crash recovery.
  489. @return TRUE if trx is an incomplete transaction that is being rolled
  490. back in crash recovery */
  491. ibool
  492. trx_is_recv(
  493. /*========*/
  494. const trx_t* trx) /*!< in: transaction */
  495. {
  496. return(trx == trx_roll_crash_recv_trx);
  497. }
  498. /*******************************************************************//**
  499. Returns a transaction savepoint taken at this point in time.
  500. @return savepoint */
  501. trx_savept_t
  502. trx_savept_take(
  503. /*============*/
  504. trx_t* trx) /*!< in: transaction */
  505. {
  506. trx_savept_t savept;
  507. savept.least_undo_no = trx->undo_no;
  508. return(savept);
  509. }
  510. /*******************************************************************//**
  511. Roll back an active transaction. */
  512. static
  513. void
  514. trx_rollback_active(
  515. /*================*/
  516. trx_t* trx) /*!< in/out: transaction */
  517. {
  518. mem_heap_t* heap;
  519. que_fork_t* fork;
  520. que_thr_t* thr;
  521. roll_node_t* roll_node;
  522. const trx_id_t trx_id = trx->id;
  523. ut_ad(trx_id);
  524. heap = mem_heap_create(512);
  525. fork = que_fork_create(NULL, NULL, QUE_FORK_RECOVERY, heap);
  526. fork->trx = trx;
  527. thr = que_thr_create(fork, heap, NULL);
  528. roll_node = roll_node_create(heap);
  529. thr->child = roll_node;
  530. roll_node->common.parent = thr;
  531. trx->graph = fork;
  532. ut_a(thr == que_fork_start_command(fork));
  533. trx_roll_crash_recv_trx = trx;
  534. const bool dictionary_locked = trx_get_dict_operation(trx)
  535. != TRX_DICT_OP_NONE;
  536. if (dictionary_locked) {
  537. row_mysql_lock_data_dictionary(trx);
  538. }
  539. que_run_threads(thr);
  540. ut_a(roll_node->undo_thr != NULL);
  541. que_run_threads(roll_node->undo_thr);
  542. que_graph_free(
  543. static_cast<que_t*>(roll_node->undo_thr->common.parent));
  544. if (UNIV_UNLIKELY(!trx_rollback_finish(trx))) {
  545. ut_ad(!dictionary_locked);
  546. goto func_exit;
  547. }
  548. ut_a(trx->lock.que_state == TRX_QUE_RUNNING);
  549. if (!dictionary_locked || !trx->table_id) {
  550. } else if (dict_table_t* table = dict_table_open_on_id(
  551. trx->table_id, TRUE, DICT_TABLE_OP_NORMAL)) {
  552. ib::info() << "Dropping table " << table->name
  553. << ", with id " << trx->table_id
  554. << " in recovery";
  555. dict_table_close_and_drop(trx, table);
  556. trx_commit_for_mysql(trx);
  557. }
  558. ib::info() << "Rolled back recovered transaction " << trx_id;
  559. func_exit:
  560. if (dictionary_locked) {
  561. row_mysql_unlock_data_dictionary(trx);
  562. }
  563. mem_heap_free(heap);
  564. trx_roll_crash_recv_trx = NULL;
  565. }
  566. struct trx_roll_count_callback_arg
  567. {
  568. uint32_t n_trx;
  569. uint64_t n_rows;
  570. trx_roll_count_callback_arg(): n_trx(0), n_rows(0) {}
  571. };
  572. static my_bool trx_roll_count_callback(rw_trx_hash_element_t *element,
  573. trx_roll_count_callback_arg *arg)
  574. {
  575. mutex_enter(&element->mutex);
  576. if (trx_t *trx= element->trx)
  577. {
  578. if (trx->is_recovered && trx_state_eq(trx, TRX_STATE_ACTIVE))
  579. {
  580. arg->n_trx++;
  581. arg->n_rows+= trx->undo_no;
  582. }
  583. }
  584. mutex_exit(&element->mutex);
  585. return 0;
  586. }
  587. /** Report progress when rolling back a row of a recovered transaction. */
  588. void trx_roll_report_progress()
  589. {
  590. ib_time_t time = ut_time();
  591. mutex_enter(&recv_sys.mutex);
  592. bool report = recv_sys.report(time);
  593. mutex_exit(&recv_sys.mutex);
  594. if (report) {
  595. trx_roll_count_callback_arg arg;
  596. /* Get number of recovered active transactions and number of
  597. rows they modified. Numbers must be accurate, because only this
  598. thread is allowed to touch recovered transactions. */
  599. trx_sys.rw_trx_hash.iterate_no_dups(
  600. reinterpret_cast<my_hash_walk_action>
  601. (trx_roll_count_callback), &arg);
  602. if (arg.n_rows > 0) {
  603. service_manager_extend_timeout(
  604. INNODB_EXTEND_TIMEOUT_INTERVAL,
  605. "To roll back: " UINT32PF " transactions, "
  606. UINT64PF " rows", arg.n_trx, arg.n_rows);
  607. }
  608. ib::info() << "To roll back: " << arg.n_trx
  609. << " transactions, " << arg.n_rows << " rows";
  610. }
  611. }
  612. static my_bool trx_rollback_recovered_callback(rw_trx_hash_element_t *element,
  613. std::vector<trx_t*> *trx_list)
  614. {
  615. mutex_enter(&element->mutex);
  616. if (trx_t *trx= element->trx)
  617. {
  618. mutex_enter(&trx->mutex);
  619. if (trx->is_recovered && trx_state_eq(trx, TRX_STATE_ACTIVE))
  620. trx_list->push_back(trx);
  621. mutex_exit(&trx->mutex);
  622. }
  623. mutex_exit(&element->mutex);
  624. return 0;
  625. }
  626. /**
  627. Rollback any incomplete transactions which were encountered in crash recovery.
  628. If the transaction already was committed, then we clean up a possible insert
  629. undo log. If the transaction was not yet committed, then we roll it back.
  630. Note: For XA recovered transactions, we rely on MySQL to
  631. do rollback. They will be in TRX_STATE_PREPARED state. If the server
  632. is shutdown and they are still lingering in trx_sys_t::trx_list
  633. then the shutdown will hang.
  634. @param[in] all true=roll back all recovered active transactions;
  635. false=roll back any incomplete dictionary transaction
  636. */
  637. void trx_rollback_recovered(bool all)
  638. {
  639. std::vector<trx_t*> trx_list;
  640. ut_a(srv_force_recovery < SRV_FORCE_NO_TRX_UNDO);
  641. /*
  642. Collect list of recovered ACTIVE transaction ids first. Once collected, no
  643. other thread is allowed to modify or remove these transactions from
  644. rw_trx_hash.
  645. */
  646. trx_sys.rw_trx_hash.iterate_no_dups(reinterpret_cast<my_hash_walk_action>
  647. (trx_rollback_recovered_callback),
  648. &trx_list);
  649. while (!trx_list.empty())
  650. {
  651. trx_t *trx= trx_list.back();
  652. trx_list.pop_back();
  653. ut_ad(trx);
  654. ut_d(trx_mutex_enter(trx));
  655. ut_ad(trx->is_recovered && trx_state_eq(trx, TRX_STATE_ACTIVE));
  656. ut_d(trx_mutex_exit(trx));
  657. if (!srv_is_being_started && !srv_undo_sources && srv_fast_shutdown)
  658. goto discard;
  659. if (all || trx_get_dict_operation(trx) != TRX_DICT_OP_NONE)
  660. {
  661. trx_rollback_active(trx);
  662. if (trx->error_state != DB_SUCCESS)
  663. {
  664. ut_ad(trx->error_state == DB_INTERRUPTED);
  665. trx->error_state= DB_SUCCESS;
  666. ut_ad(!srv_undo_sources);
  667. ut_ad(srv_fast_shutdown);
  668. discard:
  669. trx_sys.deregister_rw(trx);
  670. trx_free_at_shutdown(trx);
  671. }
  672. else
  673. trx_free(trx);
  674. }
  675. }
  676. }
  677. /*******************************************************************//**
  678. Rollback or clean up any incomplete transactions which were
  679. encountered in crash recovery. If the transaction already was
  680. committed, then we clean up a possible insert undo log. If the
  681. transaction was not yet committed, then we roll it back.
  682. Note: this is done in a background thread.
  683. @return a dummy parameter */
  684. extern "C"
  685. os_thread_ret_t
  686. DECLARE_THREAD(trx_rollback_all_recovered)(void*)
  687. {
  688. my_thread_init();
  689. ut_ad(!srv_read_only_mode);
  690. #ifdef UNIV_PFS_THREAD
  691. pfs_register_thread(trx_rollback_clean_thread_key);
  692. #endif /* UNIV_PFS_THREAD */
  693. if (trx_sys.rw_trx_hash.size()) {
  694. ib::info() << "Starting in background the rollback of"
  695. " recovered transactions";
  696. trx_rollback_recovered(true);
  697. ib::info() << "Rollback of non-prepared transactions"
  698. " completed";
  699. }
  700. trx_rollback_is_active = false;
  701. my_thread_end();
  702. /* We count the number of threads in os_thread_exit(). A created
  703. thread should always use that to exit and not use return() to exit. */
  704. os_thread_exit();
  705. OS_THREAD_DUMMY_RETURN;
  706. }
  707. /****************************************************************//**
  708. Builds an undo 'query' graph for a transaction. The actual rollback is
  709. performed by executing this query graph like a query subprocedure call.
  710. The reply about the completion of the rollback will be sent by this
  711. graph.
  712. @return own: the query graph */
  713. static
  714. que_t*
  715. trx_roll_graph_build(
  716. /*=================*/
  717. trx_t* trx) /*!< in/out: transaction */
  718. {
  719. mem_heap_t* heap;
  720. que_fork_t* fork;
  721. que_thr_t* thr;
  722. ut_ad(trx_mutex_own(trx));
  723. heap = mem_heap_create(512);
  724. fork = que_fork_create(NULL, NULL, QUE_FORK_ROLLBACK, heap);
  725. fork->trx = trx;
  726. thr = que_thr_create(fork, heap, NULL);
  727. thr->child = row_undo_node_create(trx, thr, heap);
  728. return(fork);
  729. }
  730. /*********************************************************************//**
  731. Starts a rollback operation, creates the UNDO graph that will do the
  732. actual undo operation.
  733. @return query graph thread that will perform the UNDO operations. */
  734. static
  735. que_thr_t*
  736. trx_rollback_start(
  737. /*===============*/
  738. trx_t* trx, /*!< in: transaction */
  739. undo_no_t roll_limit) /*!< in: rollback to undo no (for
  740. partial undo), 0 if we are rolling back
  741. the entire transaction */
  742. {
  743. ut_ad(trx_mutex_own(trx));
  744. /* Initialize the rollback field in the transaction */
  745. ut_ad(!trx->roll_limit);
  746. ut_ad(!trx->in_rollback);
  747. trx->roll_limit = roll_limit;
  748. trx->in_rollback = true;
  749. ut_a(trx->roll_limit <= trx->undo_no);
  750. trx->pages_undone = 0;
  751. /* Build a 'query' graph which will perform the undo operations */
  752. que_t* roll_graph = trx_roll_graph_build(trx);
  753. trx->graph = roll_graph;
  754. trx->lock.que_state = TRX_QUE_ROLLING_BACK;
  755. return(que_fork_start_command(roll_graph));
  756. }
  757. /*********************************************************************//**
  758. Creates a rollback command node struct.
  759. @return own: rollback node struct */
  760. roll_node_t*
  761. roll_node_create(
  762. /*=============*/
  763. mem_heap_t* heap) /*!< in: mem heap where created */
  764. {
  765. roll_node_t* node;
  766. node = static_cast<roll_node_t*>(mem_heap_zalloc(heap, sizeof(*node)));
  767. node->state = ROLL_NODE_SEND;
  768. node->common.type = QUE_NODE_ROLLBACK;
  769. return(node);
  770. }
  771. /***********************************************************//**
  772. Performs an execution step for a rollback command node in a query graph.
  773. @return query thread to run next, or NULL */
  774. que_thr_t*
  775. trx_rollback_step(
  776. /*==============*/
  777. que_thr_t* thr) /*!< in: query thread */
  778. {
  779. roll_node_t* node;
  780. node = static_cast<roll_node_t*>(thr->run_node);
  781. ut_ad(que_node_get_type(node) == QUE_NODE_ROLLBACK);
  782. if (thr->prev_node == que_node_get_parent(node)) {
  783. node->state = ROLL_NODE_SEND;
  784. }
  785. if (node->state == ROLL_NODE_SEND) {
  786. trx_t* trx;
  787. ib_id_t roll_limit;
  788. trx = thr_get_trx(thr);
  789. trx_mutex_enter(trx);
  790. node->state = ROLL_NODE_WAIT;
  791. ut_a(node->undo_thr == NULL);
  792. roll_limit = node->savept ? node->savept->least_undo_no : 0;
  793. trx_commit_or_rollback_prepare(trx);
  794. node->undo_thr = trx_rollback_start(trx, roll_limit);
  795. trx_mutex_exit(trx);
  796. } else {
  797. ut_ad(node->state == ROLL_NODE_WAIT);
  798. thr->run_node = que_node_get_parent(node);
  799. }
  800. return(thr);
  801. }