PG-1658 Remove server key if it is the unused default key #484
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 this was left behind even if the default key was deleted. Check if any WAL encryption keys exist and allow removal if there are none.
https://perconadev.atlassian.net/browse/PG-1658
We do have a bug here where we will remove the key even if it was explicitly set with
pg_tde_set_server_key()
, but the same is true for the database keys, so the behavior is consistent. I will report this as a bug in jira though.