MariaDB 10.8.4

What's new in this version:

Notable Items:
InnoDB:
- InnoDB corruption due to lack of file locking
- FULLTEXT search with apostrophe, and mandatory words
- ALTER TABLE IMPORT TABLESPACE corrupts an encrypted table
- ALTER TABLE wrong-result fix
- Crash recovery fixes MDEV-28731)
- DDL crash recovery fixes MDEV-28802, MDEV-28864, MDEV-28870, MDEV-28923, MDEV-28977)
- Avoid crashes on corrupted data MDEV-18519, MDEV-21098, MDEV-22388, MDEV-28457, MDEV-28950)
- Bulk load bug fixes MDEV-28679)
- Performance fixes MDEV-28766)

Replication:
- ER_SLAVE_INCIDENT error is specified now on slave to be seen with SHOW-SLAVE-STATUS
- INCIDENT_EVENT is no longer binlogged when a being logged transaction can be safely rolledback
- sequences related row-format events are made to correspond to binlog_row_image
- Possible reason of FLUSH BINARY LOGS hang is eliminated
- Fix out-of-order gtid error in the circular semisync setup

Galera:
- Possible to write/update with read_only=ON and not a SUPER privilege
- Node crashes with Transport endpoint is not connected mysqld got signal 6
- Galera4 not able to report proper wsrep_incoming_addresses
- Galera should replicate nextval()-related changes in sequences with INCREMENT <> 0, at least NOCACHE ones with engine=InnoDB
- Add support for OpenSSL 3.0 in Galera

Optimizer:
- Server crash in JOIN_CACHE::free or in copy_fields
- Queries that use DISTINCT and an always-constant function like COLLATION(aggegate_func(...)) could cause a server crash. Note that COLLATION() is a special function - its value is constant even if its argument is not costant.
- Crash when using ANY predicand with redundant subquery in GROUP BY clause
- A query with a subuquery in this form could cause a crash:
- ... ANY (SELECT ... GROUP BY (SELECT redundant_subselect_here)) ...
- MariaDB Server SEGV on INSERT .. SELECT
- Certain queries in form "INSERT ... SELECT with_aggregate_or_window_func" could cause a crash.
- restore_prev_nj_state() doesn't update cur_sj_inner_tables correctly
- Subquery semi-join optimization could miss LooseScan or FirstMatch strategies for certain queries.
- Optimizer uses all partitions after upgrade to 10.3
- For multi-table UPDATE or DELETE queries, the optimizer failed to apply Partition Pruning optimization for the table that is updated or deleted from.
- Range optimizer regression for key IN (const, ....)
- The issue can be observed on MariaDB 10.5.9 and later versions which have the fix for MDEV-9750. That fix introduceds optimizer_max_sel_arg_weight.
- If one sets optimizer_max_sel_arg_weight to a very high value or zero (which means "unlimited") and runs queries that produce heavy-weight graphs, they can observe a performance slowdown, e.g.:
- table.keyXpartY [NOT] IN ( ... )
- Wrong result with table elimination combined with not_null_range_scan
- If one runs with optimizer_switch='not_null_range_scan=on' (which is not enabled by default), a query that does a join and has const tables could produce a wrong result.
- Assertion `tmp >= 0' failed in best_access_path
- If one uses histogram_type=JSON_HB, has collected a histogram of that type and runs a query that selects a very narrow range near histogram end, they can hit an assertion in the optimizer due to rounding errors in the histogram causing negative selectivity.

Spider:
- spider_init_sql_alloc_size and spider_buffer_size have been deprecated MDEV-28560)
- Spider's high-availability feature has been deprecated

JSON:
- JSON_TABLE: extract document fragment into JSON column

CONNECT:
- CONNECT Engine now supports INSERT IGNORE with Mysql Table type

General:
- New mariadb client option, -enable-cleartext-plugin. Option does not do anything, and is for MySQL-compatibility purposes only.
- Crash in JSON_EXTRACT
- ALTER TABLE ALGORITHM=NOCOPY does not work after upgrade
- Server crash upon CREATE VIEW with unknown column in ON condition
- password_reuse_check plugin mixes username and password
- As per the MariaDB Deprecation Policy, this will be the last release of MariaDB 10.8 for Debian 10 "Buster" for ppc64el
- Repositories for Ubuntu 22.04 and RHEL/Rocky 9 have been added in this release

Security:
Fixes for the following security vulnerabilities:
- CVE-2022-32082
- CVE-2022-32089
- CVE-2022-32081
- CVE-2018-25032
- CVE-2022-32091