mirror of
https://github.com/MariaDB/server.git
synced 2025-01-19 05:22:25 +01:00
f956ecd09a
Analyze table corrupts the state on data_file_length, records, index_file_length... by writing the shared state when there is an updated internal state due to inserts or deletes Fixed by synching the shared state with the internal state before writing it to disk Added test cases of 2 error cases and a normal case in new analyze test case BitKeeper/etc/logging_ok: Logging to logging@openlogging.org accepted
39 lines
1.1 KiB
Text
39 lines
1.1 KiB
Text
#
|
|
# Bug #10901 Analyze Table on new table destroys table
|
|
# This is minimal test case to get error
|
|
# The problem was that analyze table wrote the shared state to the file and this
|
|
# didn't include the inserts while locked. A check was needed to ensure that
|
|
# state information was not updated when executing analyze table for a locked table.
|
|
# The analyze table had to be within locks and check table had to be after unlocking
|
|
# since then it brings the wrong state from disk rather than from the currently
|
|
# correct internal state. The insert is needed since it changes the file state,
|
|
# number of records.
|
|
# The fix is to synchronise the state of the shared state and the current state before
|
|
# calling mi_state_info_write
|
|
#
|
|
create table t1 (a bigint);
|
|
lock tables t1 write;
|
|
insert into t1 values(0);
|
|
analyze table t1;
|
|
unlock tables;
|
|
check table t1;
|
|
|
|
drop table t1;
|
|
|
|
create table t1 (a bigint);
|
|
insert into t1 values(0);
|
|
lock tables t1 write;
|
|
delete from t1;
|
|
analyze table t1;
|
|
unlock tables;
|
|
check table t1;
|
|
|
|
drop table t1;
|
|
|
|
create table t1 (a bigint);
|
|
insert into t1 values(0);
|
|
analyze table t1;
|
|
check table t1;
|
|
|
|
drop table t1;
|
|
|