MariaDB

maria:bb-10.4-MDEV-28314

  1. Git
  2. lp:maria
  3. bb-10.4-MDEV-28314
Last commit made on 2022-04-19
Get this branch:
git clone -b bb-10.4-MDEV-28314 https://git.launchpad.net/maria

Branch merges

Branch information

Name:
bb-10.4-MDEV-28314
Repository:
lp:maria

Recent commits

1f8fb6c... by Jan Lindström

MDEV-28314 : The Galera cluster primary node goes into hang mode when innodb_encryption_threads is enabled

When we enable writes after Galera SST srv_n_fil_crypt_threads needs
to be set temporally to 0 (as was done when writes were disabled)
to make sure that encryption threads will be really started based
on old value.

Fix provided by Marko Mäkelä and added a test case.

89b1172... by Jan Lindström

MDEV-28329 : galera_3nodes.galera_garbd_backup fails with extra connection lines

Add missing connection lines to result set

39cc254... by Oleg Smirnov

MDEV-24529 Assertion failed in vers_select_conds_t::print

This commit adds processing of SYSTEM_TIME_BEFORE and SYSTEM_TIME_HISTORY
to vers_select_conds_t::print().

8a322b6... by Daniele Sciascia <email address hidden>

Disable galera_bf_abort_ps_bind under --ps-protocol

3327bb6... by Rucha Deodhar <email address hidden>

MDEV-22266: Diagnostics_area::sql_errno() const: Assertion
`m_status == DA_ERROR' failed on SELECT after setting tmp_disk_table_size.

Analysis: Mismatch in number of warnings between "194 warnings" vs
"64 rows in set" is because of max_error_count variable which has default
value of 64.
About the corrupted tables, the error that occurs because of insufficient
tmp_disk_table_size variable is not reported correctly and we continue to
execute the statement. But because the previous error (about table being
full)is not reported correctly, this error moves up the stack and is
wrongly reported as parsing error later on while parsing frm file of one
of the information schema table. This parsing error gives corrupted table
error.
As for the innodb error, it occurs even when tmp_disk_table_size is not
insufficient is default but the internal error handler takes care of it
and the error doesn't show. But when tmp_disk_table_size is insufficient,
the fatal error which wasn't reported correctly moves up the stack so
internal error handler is not called. So it shows errors.
Fix: Report the error correctly.

b2ecb62... by Oleg Smirnov

Remove a garbage file from mysql-test

7b95731... by Marko Mäkelä

Merge 10.3 into 10.4

3c99a48... by Jan Lindström

MDEV-28247 : Disable background ibuf merge during Galera SST

This failure was caused by MDEV-25975, which removed the parameter
innodb_disallow_writes.

Added a check for wsrep_sst_disable_writes to the function
ibuf_merge_in_background().

7355f7b... by Alexander Barkov

Adding MTR tests to cover how keywords of different kinds behave in various contexts

cbdf62a... by Marko Mäkelä

MDEV-25975 merge fixup