[MDEV-16998] Allow logging of plaintext InnoDB tables during startup Created: 2018-08-16  Updated: 2018-08-16

Status: Open
Project: MariaDB Server
Component/s: Encryption
Fix Version/s: None

Type: Task Priority: Minor
Reporter: Ceri Williams Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: innodb_encrypt_tables

Issue Links:
Relates
relates to MDEV-16997 Conflicting value definitions for inn... Closed

 Description   

When changing the encryption status of the server to remove encryption we see notification about the redo log:

2018-08-16 10:42:12 0 [Note] InnoDB: Removing redo log encryption: 2*50331648 bytes; LSN=1643709

However, we don't see any notification about any tables that have been marked as ENCRYPTED=NO whilst automatic and enforce encryption is set with innodb_encrypt_tables=FORCE.

This could leave data in an unexpected state, particularly if reading part of the documentation that implies access could be prevented with FORCE (MDEV-16997).

Perhaps due to the potential number of tables that could me marked to avoid encryption, logging of such information would best be performed via a configurable option so that it can be turned on/off as required.


Generated at Thu Feb 08 08:33:08 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.