bb-10.4-MDEV-29602 : lp:maria : Git : Code : MariaDB

Get this branch:: git clone -b bb-10.4-MDEV-29602 https://git.launchpad.net/maria

Branch merges

Branch information

Name:: bb-10.4-MDEV-29602

Repository:: lp:maria

Recent commits

d6db707... by Jan Lindström on 2022-10-11

MDEV-29602 : Galera debug build crashes when the spider plugin is enabled

Spider system tables should be created so that wsrep_on=OFF.

f6f9b7f... by Jan Lindström on 2022-10-06

MDEV-29707 : Incorrect/bad errno on enabling wsrep_on after setting dummy wsrep_provider on non-Galera build

Fix error message to contain correct errno. This commit was
tested interactively because mtr will notice if you provide
wrong wsrep_provider in config and you may not change
wsrep_provider dynamically.

0908a04... by Jan Lindström on 2022-10-06

MDEV-25389 : Assertion `!is_thread_specific || (mysqld_server_initialized && thd)' failed in void my_malloc_size_cb_func(long long int, my_bool)

If wsrep slave thread creation fails for some reason we need to handle
this error correctly and set actual running slave threads accordingly.

e8acec8... by Jan Lindström on 2022-10-04

MDEV-26597 : Assertion `!wsrep_has_changes(thd) || (thd->lex->sql_command == SQLCOM_CREATE_TABLE && !thd->is_current_stmt_binlog_format_row())' failed.

If repl.max_ws_size is set too low following CREATE TABLE could fail
during commit. In this case wsrep_commit_empty should allow rolling
it back if provider state is s_aborted.

Furhermore, original ER_ERROR_DURING_COMMIT does not really tell anything
clear for user. Therefore, this commit adds a new error
ER_TOO_BIG_WRITESET. This will change some test cases output.

ab3ec01... by Jan Lindström on 2022-10-03

MDEV-27123 : auto_increment_increment and auto_increment_offset reset to 1 in current session after alter table on auto-increment column

Problem was that in ALTER TABLE execution variables were set
to 1 even when wsrep_auto_increment_control is OFF. We should
set them only when wsrep_auto_increment_control is ON.

7be82a1... by Jan Lindström on 2022-10-03

MDEV-29142 : Assertion `!_current_thd()' failed in void destroy_background_thd(THD*)

In test user has set WSREP_ON=OFF this causes streaming replication
recovery to fail and this caused call to unireg_abort(). However,
this call is not necessary and we can let transaction to fail. Naturally,
if real user does this he needs to bootstrap his cluster.

5f26f50... by Sergei Golubchik on 2022-10-07