mirror of
https://github.com/MariaDB/server.git
synced 2025-08-01 03:47:19 +03:00
MDEV-3837 Assertion `table->read_set == &table->def_read_set' failed on updating a performance_schema table
This was failing not only for P_S, but for any engine that had HA_PRIMARY_KEY_REQUIRED_FOR_DELETE flag set (in the tree - only P_S and federated). Because of this flag, read_set and write_set were (possibly) changed on update. But later the code modified these bitmaps and restored them to the default state, losing HA_PRIMARY_KEY_REQUIRED_FOR_DELETE related changes. sql/handler.cc: small optimization. don't change the *write* set only because all columns has to be *read*
This commit is contained in:
1
mysql-test/suite/perfschema/r/update_order-3837.result
Normal file
1
mysql-test/suite/perfschema/r/update_order-3837.result
Normal file
@ -0,0 +1 @@
|
||||
UPDATE performance_schema.setup_instruments SET timed = 'YES' ORDER BY name;
|
8
mysql-test/suite/perfschema/t/update_order-3837.test
Normal file
8
mysql-test/suite/perfschema/t/update_order-3837.test
Normal file
@ -0,0 +1,8 @@
|
||||
--source include/not_embedded.inc
|
||||
--source include/have_perfschema.inc
|
||||
|
||||
#
|
||||
# MDEV-3837 Assertion `table->read_set == &table->def_read_set' failed on updating a performance_schema table
|
||||
#
|
||||
UPDATE performance_schema.setup_instruments SET timed = 'YES' ORDER BY name;
|
||||
|
Reference in New Issue
Block a user