mirror of
https://github.com/MariaDB/server.git
synced 2025-01-17 12:32:27 +01:00
0186334ae8
is reached Problem was bad error handling, leaving some new temporary partitions locked and initialized and some not yet initialized and locked, leading to a crash when trying to unlock the not yet initialized and locked partitions Solution was to unlock the already locked partitions, and not include any of the new temporary partitions in later unlocks mysql-test/r/partition_open_files_limit.result: Bug#46922: crash when adding partitions and open_files_limit is reached New test result mysql-test/t/partition_open_files_limit-master.opt: Bug#46922: crash when adding partitions and open_files_limit is reached New test opt-file for testing when open_files_limit is reached mysql-test/t/partition_open_files_limit.test: Bug#46922: crash when adding partitions and open_files_limit is reached New test case testing when open_files_limit is reached sql/ha_partition.cc: Bug#46922: crash when adding partitions and open_files_limit is reached When cleaning up the partitions already locked need to be unlocked, and not be unlocked/closed after cleaning up.
22 lines
499 B
Text
22 lines
499 B
Text
DROP TABLE IF EXISTS `t1`;
|
|
# Bug#46922: crash when adding partitions and open_files_limit is reached
|
|
CREATE TABLE t1 (a INT PRIMARY KEY)
|
|
ENGINE=MyISAM PARTITION BY KEY () PARTITIONS 1;
|
|
INSERT INTO t1 VALUES (1), (2), (3), (4), (5), (6), (7), (8), (9), (10), (11);
|
|
# if the bug exists, then crash will happen here
|
|
ALTER TABLE t1 ADD PARTITION PARTITIONS 511;
|
|
ERROR HY000: Out of resources when opening file '<partition file>' (Errcode: 24)
|
|
SELECT * FROM t1;
|
|
a
|
|
1
|
|
10
|
|
11
|
|
2
|
|
3
|
|
4
|
|
5
|
|
6
|
|
7
|
|
8
|
|
9
|
|
DROP TABLE t1;
|