Create enforcement.md - Encryption Enforcement topic #403
Conversation
This file contains hidden or 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
populated with encryption enforcement
nastena1606
temporarily deployed
to
docs-create-enforcement - INTERNAL-pg_tde docs PR #403
Render
Destroyed
updated with future steps to enforce encrypt
…postgres into docs-create-enforcement
Codecov ReportAll modified and coverable lines are covered by tests ✅
❌ Your project status has failed because the head coverage (84.65%) is below the target coverage (90.00%). You can increase the head coverage or adjust the target coverage. Additional details and impacted files@@ Coverage Diff @@
## release-17.5.2 #403 +/- ##
==================================================
- Coverage 84.66% 84.65% -0.01%
==================================================
Files 21 21
Lines 2589 2588 -1
Branches 402 401 -1
==================================================
- Hits 2192 2191 -1
Misses 316 316
Partials 81 81
🚀 New features to boost your workflow:
|
updated with pg_tde enforce encryption option
…postgres into docs-create-enforcement
dutow
requested changes
Jun 10, 2025
removed table space encryption
updated the enforce_encryption description
Andriciuc
changed the title
added a note that clarifies unauthorized user access and how superusers can still bypass the forced encryption table creation
dutow
reviewed
Jun 11, 2025
There was a problem hiding this comment.
Now my generic problem with this PR is that this new page doesn't provide any additional information compared to the GUC page. In fact, it provides less, as the GUC page at least explains to an extent what are the different allowed scopes of the variable.
Jan asked for scenarios to be documented, I guess he meant things like:
- Specific example how to enforce encryption to the entire server
- Specific example how to enforce encryption to only a single database with
ALTER DATABASE SET - Example that superusers can override the variable at session level, so that they can create non encrypted tables in that session (the usecase I described on slack)
- Maybe also an example of enforcing encryption to a specific user with
ALTER USER
Which is basically adding actual examples to the "Use the following techniques..." section
small update to the note describing superuser actions properly
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.
Writing a general topic regarding Encrpytion Enforcement from pg_tde perspective, requires heavy review.