mirror of
https://github.com/MariaDB/server.git
synced 2025-02-07 06:12:18 +01:00
504cfa4857
The test with memory restrictions randomly works or fails in buildbot depending on server configurations. On my machine the original test worked. As the test was there to just check if the server crashes when run with small memory configurations, I disabled testing if the query would fail or not. The test still has its original purpose. Discussed with: Sergei Golubchik <serg@mariadb.org>
22 lines
1,015 B
Text
22 lines
1,015 B
Text
--source include/not_embedded.inc
|
|
--source include/have_perfschema.inc
|
|
# This does not crash on 32 bit because of less memory used
|
|
--source include/have_64bit.inc
|
|
--echo #
|
|
--echo # MDEV-33150 double-locking of LOCK_thd_kill in performance_schema.session_status
|
|
--echo #
|
|
source include/have_innodb.inc;
|
|
set @old_innodb_io_capacity=@@global.innodb_io_capacity;
|
|
set @old_innodb_io_capacity_max=@@global.innodb_io_capacity_max;
|
|
select * from performance_schema.session_status limit 0; # discover the table
|
|
set max_session_mem_used=32768;
|
|
--disable_result_log
|
|
--error 0,ER_OPTION_PREVENTS_STATEMENT
|
|
# this used to crash, when OOM happened under LOCK_thd_kill
|
|
select * from performance_schema.session_status;
|
|
--enable_result_log
|
|
# this used to cause mutex lock order violation when OOM happened under LOCK_global_system_variables
|
|
set global innodb_io_capacity_max=100;
|
|
set max_session_mem_used=default;
|
|
set global innodb_io_capacity=@old_innodb_io_capacity;
|
|
set global innodb_io_capacity_max=@old_innodb_io_capacity_max;
|