![]() ![]() InnoDB Storage Engine: A DDL operation for an InnoDB table could cause a busy MySQL server to halt with an assertion error: InnoDB: Failing assertion: trx->error_state = DB_SUCCESS The error occurred if the DDL operation was run while all 1023 undo slots were in use by concurrent transactions. ADD COLUMN could stall, eventually timing out with an Error 1005: Can't create table message referring to fil_rename_tablespace. InnoDB Storage Engine: A DDL operation such as ALTER TABLE. InnoDB Storage Engine: An erroneous assertion could occur, in debug builds only, when creating an index on a column containing zero-length values (that is, ''). In MySQL 5.1, this fix applies to the InnoDB Plugin, but not the built-in InnoDB storage engine. Now if a crash occurs at the precise moment when the column data is being transferred, the transfer will not be re-run during crash recovery. The fix corrects the order of operations for moving the column data off the original page and replacing it with a pointer. A related issue was that during such an UPDATE operation, or an INSERT operation that reused a delete-marked record, other transactions could see invalid data for the affected column, regardless of isolation level. Still, the problem could occur with any combination of InnoDB version, file format, and row format. The problem was more common with tables using ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED along with the Barracuda file format, particularly with the innodb_file_per_table setting enabled, because page allocation operations are more common as the. The pointer to the new allocated off-page data was not set up until the pages were allocated and written, potentially leading to lost data if the system crashed while the column was being moved out of the page. Important Change: InnoDB Storage Engine: When a row grew in size due to an UPDATE operation, other (non-updated) columns could be moved to off-page storage so that information about the row still fit within the constraints of the InnoDB page size. ![]() yaSSL was upgraded from version 1.7.2 to 2.2.0. See Debugging MariaDB with mysql-test-run for more information.įor End of Life releases, MariaDB Foundation will not provide security updates, however outside contributors are welcome to submit security and bug fixes and backports to no-longer maintained versions.- InnoDB Storage Engine: A deprecation warning is now issued when -ignore-builtin-innodb is used. If the bug is repeatable, it is very helpful if you create a test case for the bug for use with mysql-test-run. If you need help, ask on Zulip, or on the maria-developers mailing list. The developers are generally happy to help with verifying bugs. The Reporting Bugs page on the Knowledge Base has details on how to report a bug. The roadmap is visible on (login is required), along with estimated release dates. The current maintained versions are:Įach stable version receives bug-fixes and security fixes periodically. Now there are multiple short term releases each year, in addition to less frequent long-term ![]() Until MariaDB Server 10.6, MariaDB Server had about one stable major release every year. MariaDB Foundation ensures that MariaDB Server has a steady cadence of releases. To help with automating downloads of MariaDB Server and related files, MariaDB Foundation has exposed a REST API. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |