mariadb/mysql-test/suite/wsrep/r
Daniele Sciascia eb4123eefc More fixes to variable wsrep_on
* Disallow setting wsrep_on = 1 if wsrep_provider is unset. Also, move
  wsrep_on_basic from sys_vars to wsrep suite: this test now requires
  to run with wsrep_provider set
* Disallow setting @@session.wsrep_on = 1 when @@global.wsrep_on = 0
* Handle the case where a new connection turns @@global.wsrep_on from
  off to on. In this case we would miss a call to wsrep_open, causing
  unexpected states in wsrep::client_state (causing assertions).
* Disable wsrep.MDEV-22443 because it is no longer possible to enable
  wsrep_on, if server is started with wsrep_provider='none'

Reviewed-by: Jan Lindström <jan.lindstrom@mariadb.com>
2021-04-20 08:24:14 +03:00
..
alter_table_innodb.result
binlog_format.result
foreign_key.result
MDEV-20625.result
MDEV-22443.result
MDEV-23081.result
MDEV-23092.result
MDEV-23466.result
mdev_6832.result
mdev_7798.result
mdev_10186.result
mdev_22681.result
mysql_tzinfo_to_sql_symlink.result
mysql_tzinfo_to_sql_symlink_skip.result
plugin.result
pool_of_threads.result
trans.result
variables.result
variables_debug.result
wsrep-recover-v25,binlogon.rdiff
wsrep-recover-v25.result
wsrep-recover.result
wsrep_on_basic.result More fixes to variable wsrep_on 2021-04-20 08:24:14 +03:00
wsrep_rpl.result
wsrep_variables_no_provider.result
wsrep_variables_wsrep_off.result