mirror/mariadb
1
0
Fork 0
mirror of https://github.com/MariaDB/server.git synced 2025-03-24 16:08:42 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions1
mariadb/mysql-test/suite/encryption/t/innodb_first_page.test

23 lines
597 B
Text
Raw Normal View History

MDEV-8021 "InnoDB: Tablespace id 4 encrypted but encryption service not available. Can't continue opening tablespace" on server restart when there are encrypted tables key id was written in the wrong place on the tablespace first page (thus its value could not be read back later)
2015-05-09 11:19:36 +02:00
#
# MDEV-8021 "InnoDB: Tablespace id 4 encrypted but encryption service not available. Can't continue opening tablespace" on server restart when there are encrypted tables
#
--source include/have_innodb.inc
--source include/have_file_key_management_plugin.inc
MDEV-30119 INFORMATION_SCHEMA.INNODB_TABLESPACES_ENCRYPTION.NAME is NULL for undo tablespaces - Information_schema.innodb_tablespaces_encryption should print undo tablespace name as innodb_undo001, innodb_undo002 and soon. - Encryption test should include undo tablespaces count when the tests are waiting for the condition to check whether all tables are encrypted or decrypted.
2022-11-29 17:19:30 +05:30
--source include/innodb_undo_tablespaces.inc
MDEV-8021 "InnoDB: Tablespace id 4 encrypted but encryption service not available. Can't continue opening tablespace" on server restart when there are encrypted tables key id was written in the wrong place on the tablespace first page (thus its value could not be read back later)
2015-05-09 11:19:36 +02:00
MDEV-11873 Unnecessary InnoDB warnings upon bootstrap dict_create_or_check_foreign_constraint_tables(): Change the warning about the foreign key metadata table creation to a note. Remove messages after metadata table creation. If the creation fails, startup will abort with a message. Normally the creation succeeds on bootstrap, and the messages would only be noise. Remove the related suppressions from the tests.
2017-03-14 17:11:46 +02:00
let $datadir=`select @@datadir`;
--source include/shutdown_mysqld.inc
MDEV-8495 encryption.innodb_first_page fails sporadically in buildbot The test did not wait until the server shuts down
2015-07-17 19:20:50 +03:00
MDEV-8021 "InnoDB: Tablespace id 4 encrypted but encryption service not available. Can't continue opening tablespace" on server restart when there are encrypted tables key id was written in the wrong place on the tablespace first page (thus its value could not be read back later)
2015-05-09 11:19:36 +02:00
--remove_file $datadir/ib_logfile0
--remove_file $datadir/ibdata1
MDEV-30119 INFORMATION_SCHEMA.INNODB_TABLESPACES_ENCRYPTION.NAME is NULL for undo tablespaces - Information_schema.innodb_tablespaces_encryption should print undo tablespace name as innodb_undo001, innodb_undo002 and soon. - Encryption test should include undo tablespaces count when the tests are waiting for the condition to check whether all tables are encrypted or decrypted.
2022-11-29 17:19:30 +05:30
--remove_files_wildcard $datadir undo*
MDEV-8021 "InnoDB: Tablespace id 4 encrypted but encryption service not available. Can't continue opening tablespace" on server restart when there are encrypted tables key id was written in the wrong place on the tablespace first page (thus its value could not be read back later)
2015-05-09 11:19:36 +02:00
MDEV-11873 Unnecessary InnoDB warnings upon bootstrap dict_create_or_check_foreign_constraint_tables(): Change the warning about the foreign key metadata table creation to a note. Remove messages after metadata table creation. If the creation fails, startup will abort with a message. Normally the creation succeeds on bootstrap, and the messages would only be noise. Remove the related suppressions from the tests.
2017-03-14 17:11:46 +02:00
--source include/start_mysqld.inc
MDEV-8021 "InnoDB: Tablespace id 4 encrypted but encryption service not available. Can't continue opening tablespace" on server restart when there are encrypted tables key id was written in the wrong place on the tablespace first page (thus its value could not be read back later)
2015-05-09 11:19:36 +02:00
create table t1 (a int);
--source include/restart_mysqld.inc
drop table t1;
Reference in a new issue Copy permalink