59d827bad7
Problem: ======== After an instant ALTER TABLE that reorders or drops columns, innobase_instant_try() deletes/updates SYS_COLUMNS, SYS_VIRTUAL and SYS_TABLES.N_COLS, and only afterwards writes the hidden metadata record that describes the old column layout in the clustered index. These are separate mini-transactions within the same DDL transaction. If the server is killed after the SYS_COLUMNS/SYS_TABLES updates were made durable but before the metadata record was written, and recovery does not roll back the transaction then table's dictionary definition and its on-disk metadata record go out of sync. On the next load, btr_cur_instant_init_low() correctly detects this as "missing instant ALTER metadata" or "contains unrecognizable instant ALTER metadata" and sets table->corrupted, but it did not set table->file_unreadable. Since dict_table_t::is_readable() only tests file_unreadable, the table was left in an inconsistent corrupted-but-readable state. Solution: ========= btr_cur_instant_init_low(): Also set index->table->file_unreadable in the "missing instant ALTER metadata" and "incompatible instant ALTER metadata" error paths, consistent with every other corruption path in this function.
Code status:
ci.appveyor.com
MariaDB: The innovative open source database
MariaDB was designed as a drop-in replacement of MySQL(R) with more features, new storage engines, fewer bugs, and better performance.
MariaDB is brought to you by the MariaDB Foundation and the MariaDB Corporation. Please read the CREDITS file for details about the MariaDB Foundation, and who is developing MariaDB.
MariaDB is developed by many of the original developers of MySQL who now work for the MariaDB Corporation, the MariaDB Foundation and by many people in the community.
MySQL, which is the base of MariaDB, is a product and trademark of Oracle Corporation, Inc. For a list of developers and other contributors, see the Credits appendix. You can also run 'SHOW authors' to get a list of active contributors.
A description of the MariaDB project and a manual can be found at:
https://mariadb.com/docs/release-notes
Getting the code, building it and testing it
Refer to the following guide: https://mariadb.org/get-involved/getting-started-for-developers/get-code-build-test/ which outlines how to build the source code correctly and run the MariaDB testing framework, as well as which branch to target for your contributions.
Help
More help is available from the Maria Discuss mailing list https://lists.mariadb.org/postorius/lists/discuss.lists.mariadb.org/ and MariaDB's Zulip instance, https://mariadb.zulipchat.com/
Licensing
MariaDB is specifically available only under version 2 of the GNU General Public License (GPLv2). (I.e. Without the "any later version" clause.) This is inherited from MySQL. Please see the README file in the MySQL distribution for more information.
License information can be found in the COPYING file. Third party license information can be found in the THIRDPARTY file.
Bug Reports
Bug and/or error reports regarding MariaDB should be submitted at: https://jira.mariadb.org
For reporting security vulnerabilities see: https://mariadb.org/about/security-policy/
The code for MariaDB, including all revision history, can be found at: https://github.com/MariaDB/server