![]() ![]() MariaDB Enterprise Backup could crash when used in combination with FLUSH TABLES and UNLOCK TABLES ( MENT-438) ![]() MariaDB Enterprise Backup could encounter a deadlock if a backup is taken from a replica with slave-parallel-threads is set to a value greater than 0 ( MDEV-21255) ( MDEV-18046)Ī replication primary (master) running in semi-sync mode could crash when RESET MASTER is executed and the replica reconnects using the GTID protocol. Possible server crash if binlog_ checksum=CRC32 (default) is set and if the value for parameter pos in SHOW BINLOG EVENTS FROM pos does not point to the beginning of an event in the binary log. ( MDEV-21512)Ĭrashes could occur rarely when using ALTER TABLE. On a rollback or during a background task to purge transaction history due to a SPATIAL INDEX, the server could hang. On a rollback of a large insert or update, or during a background task to purge transaction history after a large update or delete, the server could hang. A restart was only possible after increasing innodb_ buffer_ pool_ size. ![]() During a server restart InnoDB recovery could encounter an out-of-memory condition. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |