maria:bb-10.10-midenok

Last commit made on 2023-11-14
Get this branch:
git clone -b bb-10.10-midenok https://git.launchpad.net/maria

Branch merges

Branch information

Name:
bb-10.10-midenok
Repository:
lp:maria

Recent commits

7f01ddf... by midenok

MDEV-29872 MSAN/Valgrind uninitialised value errors in TABLE::vers_switch_partition

Delayed_insert has its own THD (initialized at mysql_insert()) and
hence its own LEX. Delayed_insert initalizes a very few parameters for
LEX and 'duplicates' is not in this list. Now we copy this missing
parameter from parser LEX (as well as sql_command).

352dad8... by midenok

MDEV-31903 Server crashes in _ma_reset_history upon UNLOCK table with auto-create history partitions

When INSERT does auto-create for t1 all its handler instances are
closed by alter_close_table(). At this time down the stack
maria_close() clears share->state_history. Later when we unlock the
tables Aria transaction manager accesses old share instance (the one
before t1 was closed) and tries to reset its state_history.

The problem is maria_close() didn't remove table from transaction's
list (used_tables). The fix does _ma_remove_table_from_trnman() which
is triggered by HA_EXTRA_PREPARE_FOR_RENAME.

ae0afad... by Marko Mäkelä

MDEV-32746 SIGSEGV on recovery when using innodb_encrypt_log and PMEM

recv_ring::copy_if_needed(): If len==0, do not decrypt anything,
to avoid unnecessary work and a possible crash.

This is similar to the condition recv_buf::copy_if_needed() where
a similar condition was present since the beginning
(commit 685d958e38b825ad9829be311f26729cccf37c46).

Tested by: Matthias Leich

e6f56e3... by Oleksandr "Sanja" Byelkin

Merge branch '10.11' into mariadb-10.11.6

ecce948... by Daniel Bartholomew <email address hidden>

bump the VERSION

fecd78b... by Oleksandr "Sanja" Byelkin

Merge branch '10.10' into 10.11

04d9a46... by Oleksandr "Sanja" Byelkin

Merge branch '10.6' into 10.10

b83c379... by Oleksandr "Sanja" Byelkin

Merge branch '10.5' into 10.6

2a4c573... by Kristian Nielsen

MDEV-32728: Wrong mutex usage 'LOCK_thd_data' and 'wait_mutex'

Checking for kill with thd_kill_level() or check_killed() runs apc
requests, which takes the LOCK_thd_kill mutex. But this is dangerous,
as checking for kill needs to be called while holding many different
mutexes, and can lead to cyclic mutex dependency and deadlock.

But running apc is only "best effort", so skip running the apc if the
LOCK_thd_kill is not available. The apc will then be run on next check
of kill signal.

Signed-off-by: Kristian Nielsen <email address hidden>

6cfd2ba... by Oleksandr "Sanja" Byelkin

Merge branch '10.4' into 10.5