server
server copied to clipboard
MariaDB
MariaDB server is a community developed fork of MySQL server. Started by core members of the original MySQL team, MariaDB actively works with outside developers to deliver the most featureful, stable,...
… in EXPLAIN/ANALYZE FORMAT=JSON - [x] *The Jira issue number for this PR is: MDEV-34041* ## Description This is a WIP (work-in-progress) PR, that's why the test suite is not...
- [x] *The Jira issue number for this PR is: MDEV-34062* ## Description In MariaDB Server 10.11 (but not 10.6), copying the InnoDB write-ahead log (`innodb_logfile0`) is taking an extremely...
- [x] *The Jira issue number for this PR is: MDEV-34057* ## Description - InnoDB FTS can be in inconsistent state when sync operation terminates the server before committing the...
- [x] *The Jira issue number for this PR is: [MDEV-34234](https://jira.mariadb.org/browse/MDEV-34234)* ## Description Make lsof an optional dependency on RPM based builds. This should allow users to select if they...
- [x] *The Jira issue number for this PR is: MDEV-33935* ## Description Fixed deadlock counter incrementing on every call to cycle finding that was used multiple times during the...
- [x] *The Jira issue number for this PR is: MDEV-34156* ## Description Problem: ======= - During recovery, InnoDB fails to apply the redo log for compressed tablespace. The reason...
When there is no range nor ref condition that we may leverage for an index lookup, thne we may do a full index scan instead of a table scan. Mostly...
- [x] *The Jira issue number for this PR is: [MDEV-34214](https://jira.mariadb.org/browse/MDEV-34214)* ## Description * Pass the sst.tcert / ssl_cert (leaf certificate) to openssl verify as parameter for the "-untrusted" flag,...
- [x] *The Jira issue number for this PR is: MDEV-______* ## Description Small but important fixes to the issues discovered by production users. - fix wsrep GTID recovery procedure...
…ep_gtid_mode = 0 - [x] *The Jira issue number for this PR is: MDEV-34170* ## Description Problem was that updates to mysql.gtid_slave_pos table were replicated even when they were newer...
