Skip to content

Tags: dlenski/mariadb-server

Tags

mariadb-10.6.4

Toggle mariadb-10.6.4's commit message

Verified

This tag was signed with the committer’s verified signature.
dbart Daniel Bartholomew
MariaDB 10.6.4

mariadb-10.5.12

Toggle mariadb-10.5.12's commit message

Verified

This tag was signed with the committer’s verified signature.
dbart Daniel Bartholomew
MariaDB 10.5.12

mariadb-10.4.21

Toggle mariadb-10.4.21's commit message

Verified

This tag was signed with the committer’s verified signature.
dbart Daniel Bartholomew
MariaDB 10.4.21

mariadb-10.3.31

Toggle mariadb-10.3.31's commit message

Verified

This tag was signed with the committer’s verified signature.
dbart Daniel Bartholomew
MariaDB 10.3.31

mariadb-10.2.40

Toggle mariadb-10.2.40's commit message

Verified

This tag was signed with the committer’s verified signature.
dbart Daniel Bartholomew
MariaDB 10.2.40

mariadb-10.6.3

Toggle mariadb-10.6.3's commit message
update C/C to 3.2.3

mariadb-10.5.11

Toggle mariadb-10.5.11's commit message
MDEV-25867 main.trigger-trans failed in bb, Assertion `ticket->m_dura…

…tion == MDL_EXPLICIT' failed in MDL_context::release_lock

release MDL on the trigger as early as possible, after everything that
cannot be done concurrently was done (under MDL), but before relocking
tables.

mariadb-10.6.2

Toggle mariadb-10.6.2's commit message
update C/C

mariadb-10.4.20

Toggle mariadb-10.4.20's commit message
Merge 10.3 to 10.4

mariadb-10.3.30

Toggle mariadb-10.3.30's commit message
MDEV-25886 CHECK TABLE crash with DB_MISSING_HISTORY if innodb_read_only

Occasionally, the test innodb.alter_copy would fail in MariaDB 10.6.1,
reporting DB_MISSING_HISTORY during CHECK TABLE. It started to occur during
the development of MDEV-25180, which introduced purge_sys.stop_SYS().
If we delay purge more during DDL operations, then the test would
almost always fail. The reason is that during startup we will restore
a purge view, and CHECK TABLE would still use REPEATABLE READ
even though innodb_read_only is set and other isolation levels
than READ UNCOMMITTED are not guaranteed to work.

ha_innobase::check(): Use READ UNCOMMITTED isolation level if
innodb_read_only is set or innodb_force_recovery exceeds 3.

dict_set_corrupted(): Do not update the persistent data dictionary
if innodb_force_recovery exceeds 3.