mariadb/mysql-test/suite/perfschema/r/thread_cache.result
Marc Alff ea35bf7a71 Bug#56618 Thread_ID is not assigned in ascending sequence (after disconnect)
Before this fix, the test thread_cache failed with spurious failures.

The test used:
-- disconnect X
-- connect Y

while assuming that connection Y would reuse connection X slot in the thread cache.

For this to happen, the disconnect X operation must be given enough time to complete,
otherwise connect Y can be executed in the server before X actually finishes.

This fix uses wait conditions to make the test execution more controlled,
and more reproductible.
2010-12-01 11:10:15 +01:00

39 lines
875 B
Text

flush status;
SET @saved_thread_cache_size = @@global.thread_cache_size;
set global thread_cache_size = 0;
show variables like "thread_cache_size";
Variable_name Value
thread_cache_size 0
select @id_increment;
@id_increment
1
select @thread_id_increment;
@thread_id_increment
1
select @id_increment;
@id_increment
1
select @thread_id_increment;
@thread_id_increment
1
set global thread_cache_size = 100;
show variables like "thread_cache_size";
Variable_name Value
thread_cache_size 100
select @id_increment;
@id_increment
1
select @thread_id_increment;
@thread_id_increment
1
select @id_increment;
@id_increment
1
select @thread_id_increment;
@thread_id_increment
1
set global thread_cache_size = @saved_thread_cache_size;
show status like "performance_schema_thread%";
Variable_name Value
Performance_schema_thread_classes_lost 0
Performance_schema_thread_instances_lost 0