maria:bb-10.5-MDEV-24010

Branch merges

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related charm recipes

79086a5... by Jan Lindström on 2021-01-13

MDEV-24010 : galera_3nodes.GCF-354 MTR fails : WSREP has not yet prepared node for application use

Correct test.

8de233a... by Marko Mäkelä on 2021-01-11

Merge 10.4 into 10.5

fd5e103... by Marko Mäkelä on 2021-01-11

Merge 10.3 into 10.4

5a1a714... by Marko Mäkelä on 2021-01-11

Merge 10.2 into 10.3 (except MDEV-17556)

The fix of MDEV-17556 (commit e25623e78a3efde05e30070dc7362f8dc0d8c459
and commit 61a362c9493df63dc588fcb71409537ae56ab9c8) has been
omitted due to conflicts and will have to be applied separately later.

1015cbd... by Brad Smith on 2021-01-10

MDEV-24556: Build does not recognize powerpc64 (OpenBSD)

Reviewer: Daniel Black

3b548d3... by Vladislav Vaintroub on 2021-01-09

MDEV-24554 Do not use verisign server for authenticode timestamping

a131b97... by Daniele Sciascia <email address hidden> on 2021-01-08

Fix MTR test galera_as_slave_replay

- Galera cluster must be in node 1 and 2, and acts as slave for node 3
- Sync point commit_monitor_enter_sync was renamed to
  commit_monitor_master_enter_sync in 4.x

Reviewed-by: Jan Lindström <email address hidden>

49b8774... by Jan Lindström on 2021-01-09

MDEV-24546 : AddressSanitizer: initialization-order-fiasco on address ... in Sys_var_integer from __static_initialization_and_destruction_0, possibly inside global var wsrep_gtid_server

Galera parameter wsrep_gtid_domain_id was defined using a class where
actual parameter was not a first member. Fixed this by using normal
variable and assigning this value to class member value.

775fcce... by Jan Lindström on 2020-12-17

MDEV-23536 : Race condition between KILL and transaction commit

A race condition may occur between the execution of transaction commit,
and an execution of a KILL statement that would attempt to abort that
transaction.

MDEV-17092 worked around this race condition by modifying InnoDB code.
After that issue was closed, Sergey Vojtovich pointed out that this
race condition would better be fixed above the storage engine layer:

If you look carefully into the above, you can conclude that
thd->free_connection() can be called concurrently with
KILL/thd->awake(). Which is the bug. And it is partially fixed in
THD::~THD(), that is destructor waits for KILL completion:

Fix: Add necessary mutex operations to THD::free_connection()
and move WSREP specific code also there. This ensures that no
one is using THD while we do free_connection(). These mutexes
will also ensures that there can't be concurrent KILL/THD::awake().

innobase_kill_query
  We can now remove usage of trx_sys_mutex introduced on MDEV-17092.

trx_t::free()
  Poison trx->state and trx->mysql_thd

This patch is validated with an RQG run similar to the one that
reproduced MDEV-17092.

18254c1... by Marko Mäkelä on 2021-01-08

Cleanup: Remove unused symbol QUE_THR_PROCEDURE_WAIT