-
Notifications
You must be signed in to change notification settings - Fork 246
From the perspective of TDE function implementation, the sequence of operations when reading data is: read data -> decompress data -> decrypt data; when writing data, the sequence is: encrypt data -> compress data -> write data to disk. Placing the encryption operation before the compression operation almost renders the compression ineffective. Why is this processing method adopted?
All reactions
Replies: 1 comment 3 replies
Generally, data should be compressed first and then encrypted when written.
However, when TDE was first designed, it mainly aimed to support heap tables, which do not support compression.
AO/AOCS tables were implemented later; to keep the code simple, the same codebase was reused, so the order of compression and encryption was not taken into account.
All reactions
Do you have any plans to readjust the processing sequence in the future?
All reactions
I am working on other projects and have no plans to process the encryption and compression sequence issues.
All reactions
Hi @wsg314 welcome to contribute if you have a chance. 🫶