8/14/2023 0 Comments Dev mysql downloadsIf 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: 10.3, 10.4, 10.5, 10.6, 10.11 (maintained for 5 years), 10.8, 10.9, 10.10, 11.0 (maintained for one year), and the development version is 11.1.Įach stable version receives bug-fixes and security fixes periodically. With the new release model, there will be multiple short-term releases each year, in addition to less frequent long-term Until MariaDB Server 10.6, MariaDB Server has had about one stable major release every year. MariaDB Foundation ensures that MariaDB Server has a steady cadence of releases. MySQL Community Server 5.5.To help with automating downloads of MariaDB Server and related files, MariaDB Foundation has exposed a REST API. * SHOW TABLES was very slow unless the required information was already in the disk cache. Note : Tables using the InnoDB storage engine are not affected by this issue, since InnoDB does not allow the creation of a composite key that includes an AUTO_INCREMENT column, where this column is not the first column in the key. For more information, see Section 16.1.2.3, “Determination of Safe and Unsafe Statements in Binary Logging”, as well as Section 16.4.1.1, “Replication and AUTO_INCREMENT”. Such statements are now marked as unsafe and fail with an error when using the STATEMENT binary logging format. * Replication: An INSERT into a table that has a composite primary key that includes an AUTO_INCREMENT column that is not the first column of this composite key is not safe for statement-based binary logging or replication. * Replication: Statements using AUTO_INCREMENT, LAST_INSERT_ID(), RAND(), or user variables could be applied in the wrong context on the slave when using statement-based replication and replication filtering server options (see Section 16.2.3, “How Servers Evaluate Replication Filtering Rules”). * Replication: It was theoretically possible for concurrent execution of more than one instance of SHOW BINLOG EVENTS to crash the MySQL Server. It also makes InnoDB recognize the syntax CHECK TABLE QUICK, which avoids the possibility of the timeout entirely. The fix relaxes the locking performed on the table being checked, which makes the timeout less likely. For typical storage devices, the issue could occur for tables that exceeded approximately 200 or 350 GB, depending on I/O speed. * InnoDB: The CHECK TABLE statement could fail for a large InnoDB table due to a timeout value of 2 hours. The message suggested a potential problem with the data dictionary, when no such problem existed. * InnoDB: The error handling and message was improved for attempting to create a foreign key with a column referencing itself. Its value should never exceed the value of Innodb_pages_written. * InnoDB: The Innodb_buffer_pool_pages_flushed status variable was incorrectly set to twice the value it should be. As explained in Section 14.3.9.2, “Consistent Nonlocking Reads”, DML statements within a REPEATABLE READ transaction apply to rows committed by other transactions, even if a query could not see those rows. * InnoDB: In a transaction using the REPEATABLE READ isolation level, an UPDATE or DELETE statement for an InnoDB table could sometimes overlook rows recently committed by other transactions. This fix increases the rate of flushing in cases where compression is used and the data set is larger than the buffer pool, leading to eviction. * Performance: InnoDB: Improved the algorithm related to adaptive flushing.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |