summaryrefslogtreecommitdiff
path: root/mysql-test/suite/encryption
Commit message (Collapse)AuthorAgeFilesLines
...
| | | * | | | | Merge 10.6 into 10.7Marko Mäkelä2022-11-281-1/+9
| | | |\ \ \ \ \ | | | | |/ / / /
| | | | * | | | Merge 10.5 into 10.6Marko Mäkelä2022-11-281-1/+9
| | | | |\ \ \ \ | | | | | |/ / /
| | | | | * | | MDEV-24412 InnoDB: Upgrade after a crash is not supportedMarko Mäkelä2022-11-281-1/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | recv_log_recover_10_4(): Widen the operand of bitwise and to 64 bits, so that the upgrade check will work when the redo log record is located more than 4 gigabytes from the start of the first file.
* | | | | | | | Merge 10.10 into 10.11Marko Mäkelä2022-11-242-6/+6
|\ \ \ \ \ \ \ \ | |/ / / / / / /
| * | | | | | | Merge 10.8 into 10.9Marko Mäkelä2022-11-242-6/+6
| |\ \ \ \ \ \ \ | | |/ / / / / /
| | * | | | | | Merge 10.7 into 10.8Marko Mäkelä2022-11-242-6/+6
| | |\ \ \ \ \ \ | | | |/ / / / /
| | | * | | | | Merge 10.6 into 10.7Marko Mäkelä2022-11-242-6/+6
| | | |\ \ \ \ \ | | | | |/ / / /
| | | | * | | | Merge 10.5 into 10.6Marko Mäkelä2022-11-232-6/+6
| | | | |\ \ \ \ | | | | | |/ / /
| | | | | * | | MDEV-30068 Confusing error message when encryption is not available on recoveryMarko Mäkelä2022-11-222-6/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | fil_name_process(): If fil_ibd_load() returns FIL_LOAD_INVALID, display the file name and the tablespace identifier.
* | | | | | | | Merge 10.10 into 10.11Marko Mäkelä2022-11-211-0/+14
|\ \ \ \ \ \ \ \ | |/ / / / / / /
| * | | | | | | Merge 10.8 into 10.9Marko Mäkelä2022-11-211-0/+14
| |\ \ \ \ \ \ \ | | |/ / / / / /
| | * | | | | | Merge 10.7 into 10.8Marko Mäkelä2022-11-171-0/+14
| | |\ \ \ \ \ \ | | | |/ / / / /
| | | * | | | | Merge 10.6 into 10.7Marko Mäkelä2022-11-171-0/+14
| | | |\ \ \ \ \ | | | | |/ / / /
| | | | * | | | Merge 10.5 into 10.6Marko Mäkelä2022-11-172-11/+1
| | | | |\ \ \ \ | | | | | |/ / /
| | | | | * | | MDEV-29982 fixup: Relax the testMarko Mäkelä2022-11-172-11/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The log overwrite warnings are not being reliably emitted in all debug-instrumented environments. It may be related to the scheduling of some InnoDB internal activity, such as the purging of committed transaction history.
| | | | * | | | Merge 10.5 into 10.6Marko Mäkelä2022-11-142-0/+24
| | | | |\ \ \ \ | | | | | |/ / /
| | | | | * | | MDEV-29982 Improve the InnoDB log overwrite error messageMarko Mäkelä2022-11-142-0/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The InnoDB write-ahead log ib_logfile0 is of fixed size, specified by innodb_log_file_size. If the tail of the log manages to overwrite the head (latest checkpoint) of the log, crash recovery will be broken. Let us clarify the messages about this, including adding a message on the completion of a log checkpoint that notes that the dangerous situation is over. To reproduce the dangerous scenario, we will introduce the debug injection label ib_log_checkpoint_avoid_hard, which will avoid log checkpoints even harder than the previous ib_log_checkpoint_avoid. log_t::overwrite_warned: The first known dangerous log sequence number. Set in log_close() and cleared in log_write_checkpoint_info(), which will output a "Crash recovery was broken" message.
* | | | | | | | Merge branch '10.10' into 10.11Oleksandr Byelkin2022-11-029-0/+59
|\ \ \ \ \ \ \ \ | |/ / / / / / /
| * | | | | | | Merge branch '10.8' into 10.9Oleksandr Byelkin2022-11-019-0/+59
| |\ \ \ \ \ \ \ | | |/ / / / / /
| | * | | | | | Merge 10.7 into 10.8Marko Mäkelä2022-11-019-0/+59
| | |\ \ \ \ \ \ | | | |/ / / / /
| | | * | | | | Merge branch '10.6' into 10.7Oleksandr Byelkin2022-10-299-0/+59
| | | |\ \ \ \ \ | | | | |/ / / /
| | | | * | | | Merge 10.5 into 10.6Marko Mäkelä2022-10-259-0/+59
| | | | |\ \ \ \ | | | | | |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | To prevent ASAN heap-use-after-poison in the MDEV-16549 part of ./mtr --repeat=6 main.derived the initialization of Name_resolution_context was cleaned up.
| | | | | * | | Merge 10.4 into 10.5Marko Mäkelä2022-10-259-0/+59
| | | | | |\ \ \ | | | | | | |/ /
| | | | | | * | Merge 10.3 into 10.4Marko Mäkelä2022-10-259-0/+59
| | | | | | |\ \ | | | | | | | |/
| | | | | | | * MDEV-25343 Error log message not helpful when filekey is too longkurt2022-10-219-0/+59
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add a test related to the Encrypted Key File by following instructions in kb example https://mariadb.com/kb/en/file-key-management-encryption-plugin/#creating-the-key-file Reviewed by Daniel Black (with minor formatting and re-org of duplicate close(f) calls).
| | | | | | | * Revert "MDEV-25343 add read secret size in file key plugin"Daniel Black2022-10-194-21/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This reverts commit cee7175b79a22c29a82ef328aba208f90afcea86.
| | | | | | | * MDEV-25343 add read secret size in file key pluginkurt2022-10-194-0/+21
| | | | | | | |
* | | | | | | | MDEV-28926 Add time spent on query optimizer to JSON ANALYZE (#2193)Luis Eduardo Oliveira Lizardo2022-10-261-0/+3
|/ / / / / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Add query optimizer timer to ANALYZE FORMAT=JSON * Adapt tests and results * Change logic to always close the writer after printing query blocks
* | | | | | | Merge branch '10.8' into 10.9Oleksandr Byelkin2022-10-042-2/+0
|\ \ \ \ \ \ \ | |/ / / / / /
| * | | | | | Merge branch '10.7' into 10.8Oleksandr Byelkin2022-10-042-2/+0
| |\ \ \ \ \ \ | | |/ / / / /
| | * | | | | Merge branch '10.6' into 10.7Oleksandr Byelkin2022-10-042-2/+0
| | |\ \ \ \ \ | | | |/ / / /
| | | * | | | Merge 10.5 into 10.6Marko Mäkelä2022-09-262-2/+0
| | | |\ \ \ \ | | | | |/ / /
| | | | * | | Merge 10.4 into 10.5Marko Mäkelä2022-09-262-2/+0
| | | | |\ \ \ | | | | | |/ /
| | | | | * | MDEV-29613 Improve WITH_DBUG_TRACE=OFFMarko Mäkelä2022-09-232-2/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In commit 28325b08633372cc343dfcbc41fe252020cf6e6e a compile-time option was introduced to disable the macros DBUG_ENTER and DBUG_RETURN or DBUG_VOID_RETURN. The parameter name WITH_DBUG_TRACE would hint that it also covers DBUG_PRINT statements. Let us do that: WITH_DBUG_TRACE=OFF shall disable DBUG_PRINT() as well. A few InnoDB recovery tests used to check that some output from DBUG_PRINT("ib_log", ...) is present. We can live without those checks. Reviewed by: Vladislav Vaintroub
* | | | | | | Merge 10.8 into 10.9Marko Mäkelä2022-09-2118-88/+88
|\ \ \ \ \ \ \ | |/ / / / / /
| * | | | | | Merge 10.7 into 10.8Marko Mäkelä2022-09-2118-88/+88
| |\ \ \ \ \ \ | | |/ / / / /
| | * | | | | Merge 10.6 into 10.7Marko Mäkelä2022-09-2118-88/+88
| | |\ \ \ \ \ | | | |/ / / /
| | | * | | | Merge 10.5 into 10.6Marko Mäkelä2022-09-2018-88/+88
| | | |\ \ \ \ | | | | |/ / /
| | | | * | | Merge remote-tracking branch 'origin/10.4' into 10.5Alexander Barkov2022-09-1418-88/+88
| | | | |\ \ \ | | | | | |/ /
| | | | | * | Merge 10.3 into 10.4Marko Mäkelä2022-09-1318-88/+88
| | | | | |\ \ | | | | | | |/
| | | | | | * MDEV-29446 Change SHOW CREATE TABLE to display default collationAlexander Barkov2022-09-1218-88/+88
| | | | | | |
* | | | | | | Merge 10.8 into 10.9Jan Lindström2022-09-063-0/+3
|\ \ \ \ \ \ \ | |/ / / / / /
| * | | | | | Merge 10.7 into 10.8Jan Lindström2022-09-053-0/+3
| |\ \ \ \ \ \ | | |/ / / / /
| | * | | | | Merge 10.6 into 10.7Jan Lindström2022-09-053-0/+3
| | |\ \ \ \ \ | | | |/ / / /
| | | * | | | MDEV-29374 InnoDB recovery fails with "Data structure corruption"Marko Mäkelä2022-08-313-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | recv_sys_t::free_corrupted_page(): Identify the corrupted page in an error or warning message. buf_page_free(): Just in case, register the page as modified. This should already have been done in mtr_t::free() as part of fseg_free_page_low(). mtr_t::memo_push(): Simplify a condition, so that when invoked with MTR_MEMO_PAGE_X_MODIFY, we will do the right thing. fseg_free_page_low(): Remove an accidentally added return statement that prevented mtr_t::free() from being called. This fixes a regression that was introduced in commit 0b47c126e31cddda1e94588799599e138400bcf8 (MDEV-13542).
* | | | | | | Merge branch '10.8' into 10.9Oleksandr Byelkin2022-08-0912-12/+12
|\ \ \ \ \ \ \ | |/ / / / / /
| * | | | | | Merge branch '10.7' into 10.8Oleksandr Byelkin2022-08-0912-12/+12
| |\ \ \ \ \ \ | | |/ / / / /
| | * | | | | Merge branch '10.6' into 10.7Oleksandr Byelkin2022-08-0812-12/+12
| | |\ \ \ \ \ | | | |/ / / /
| | | * | | | MDEV-13542 fixup: Improve a recovery error messageMarko Mäkelä2022-08-0512-12/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | A message used to say "failed to read or decrypt" but the "or decrypt" part was removed in commit 0b47c126e31cddda1e94588799599e138400bcf8 without adjusting rarely needed error message suppressions in some encryption tests. Let us improve the error message so that it mentions the file name, and adjust all error message suppressions in tests. Thanks to Oleksandr Byelkin for noticing one test failure.
* | | | | | | Merge 10.8 into 10.9Marko Mäkelä2022-07-283-0/+19
|\ \ \ \ \ \ \ | |/ / / / / /
View Lorry Controller Status