mirror of
https://github.com/MariaDB/server.git
synced 2025-01-31 02:51:44 +01:00
7b16291c36
In async IO completion code, after reading a page,Innodb can wait for completion of other bufferpool reads. This is for example what happens if change-buffering is active. Innodb on Windows could deadlock, as it did not have dedicated threads for processing change buffer asynchronous reads. The fix for that is to have windows now has the same background threads, including dedicated thread for ibuf, and log AIOs. The ibuf/read completions are now dispatched to their threads with PostQueuedCompletionStatus(), the write and log completions are processed in thread where they arrive.
28 lines
No EOL
774 B
Text
28 lines
No EOL
774 B
Text
--source include/windows.inc
|
|
|
|
# Deadlock in conjunction with the innodb change buffering.
|
|
|
|
# When innodb change buffering kicks in, i.e secondary non-unique index
|
|
# does not fit into the bufferpool, then, on Windows, innodb
|
|
# background threads could deadlock whenever index page is
|
|
# read, and the page needs load/merge change buffer.
|
|
# The test tries to reproduce this situation, by creating index
|
|
# that does not fit into bufferpool, and doing a large update.
|
|
|
|
CREATE TABLE t1(
|
|
a INT AUTO_INCREMENT PRIMARY KEY,
|
|
b CHAR(255),
|
|
INDEX(b))
|
|
ENGINE=InnoDB;
|
|
|
|
INSERT INTO t1(b) SELECT UUID();
|
|
BEGIN;
|
|
let $i=`select cast(log2(@@innodb_buffer_pool_size/255) as int)`;
|
|
while ($i)
|
|
{
|
|
INSERT INTO t1(b) SELECT UUID() FROM t1;
|
|
dec $i;
|
|
}
|
|
COMMIT;
|
|
UPDATE t1 SET b=UUID();
|
|
DROP TABLE t1; |