Handle recreated relations in smgr encryption #315
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dutow
force-pushed
the
smgrcreatefix
branch
2 times, most recently
from
fb22f4f to
6bb4c11
Compare
dAdAbird
approved these changes
Oct 21, 2024
dutow
force-pushed
the
smgrcreatefix
branch
5 times, most recently
from
ed31d2e to
c9c0294
Compare
Previously operations that created a new relation file for some reason (truncate for example) resulted in a new unencrypted file, even if the original file was encrypted. This commit changes this behavior to properly create a new internal key for the new internal file in this case. This only works in pair with the related core change in the postgres repository.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously operations that created a new relation file for some reason (truncate for example) resulted in a new unencrypted file, even if the original file was encrypted.
This commit changes this behavior to properly create a new internal key for the new internal file in this case.
This only works in pair with the related core change in the postgres repository.