![]() ![]() ![]() Locking for the internal queries has been improved to fix the issue Replication: Internal queries from Group Replication to the Performance Schema for statistics on local group members failed if they occurred simultaneously with changes to the group's membership. The generated DELETE statement is now logged with accompanying BEGIN and COMMIT statements, and the resulting transaction is flushed to the binary log immediately after it is written to the statement cache, so that it always receives its own GTID and is kept separate from other transactions Also, in some situations, the generated DELETE statement could consume the GTID intended for the transaction that triggered it. Previously, the generated DELETE statement was written to the binary log statement cache for the current session, which could result in it being logged together with other statements under the same GTID, or logged without BEGIN and COMMIT statements. To replicate this effect to replicas, the first time that the source uses a given MEMORY table after startup, it notifies replicas that the table must be emptied by writing a DELETE statement for that table to the binary log. Replication: When a replication source server shuts down and restarts, its MEMORY tables become empty. Our thanks to Quanan Han for the suggestion The index was used for handling the ORDER BY The column used in the ORDER BY was the rightmost column in the index The column with the prefix was the leftmost column in the index The query's WHERE clause contained an equality condition on the prefixed column The table had a composite index with a prefix on one of the columns Partitioning: A query against a partitioned table, which used an ORDER BY, returned unordered results under the following conditions: ![]() InnoDB: A fatal “page still fixed or dirty” error occurred during shutdown InnoDB: The server failed intermittently with an “ibuf cursor restoration fails” error InnoDB: Purge thread activity was excessive when the history list length approached zero, wasting CPU resource and causing mutex contention Thanks to Fungo Wang for the contribution The METRIC_AVG_VALUE_RESET field was incorrectly marked as NULL. InnoDB: The INNODB_METRICS table AVG_COUNT_RESET value for a counter defined as a module owner reported NULL. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |