PG-1013 Added build comparison table, moved features from index to comparison #280
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
|
Performance test results: |
nastena1606
force-pushed
the
PG-1013-DOC-pg_tde-for-PG17
branch
from
7cfa16f
to
ec4d32d
Compare
dAdAbird
reviewed
Sep 23, 2024
documentation/docs/features.md
Outdated
|
|
||
| | PostgreSQL Community build | Percona Server for PostgreSQL build <br> (in addition to features included in the PostgreSQL Community build)| | ||
| |----------------------|-------------------------------| | ||
| | Table encryption: <br> - data tables, <br> - TOAST tables <br> - temporary tables created during the database operation.<br><br> Metadata of those tables is not encrypted. | Index data encryption for encrypted tables | |
There was a problem hiding this comment.
Regarding the encryption of TMP tables in Percona Server see https://perconadev.atlassian.net/browse/PG-1001. We didn't plan to have it, but might have accidentally done it)
There was a problem hiding this comment.
Sorry i'm not following, what should be changed in the current wording?
documentation/docs/features.md
Outdated
|
|
||
| ## Future releases | ||
|
|
||
| The following is planned for future releases of `pg_tde`: | ||
|
|
||
| * Logical replication support | ||
| * | ||
| * KMIP integration for key management | ||
|
|
||
| <i warning>:material-alert: Warning:</i> Note that introducing encryption/decryption affects performance. Our benchmark tests show less than 10% performance overhead for most situations. However, in some specific applications such as those using JSONB operations, performance degradation might be higher. |
There was a problem hiding this comment.
I think this needs to be clarified to make sure that the user knows which method do we relate to
documentation/docs/features.md
Outdated
|
|
||
| ## Future releases | ||
|
|
||
| The following is planned for future releases of `pg_tde`: | ||
|
|
||
| * Logical replication support |
There was a problem hiding this comment.
for which method?
nastena1606
force-pushed
the
PG-1013-DOC-pg_tde-for-PG17
branch
from
71207a9
to
e78b293
Compare
nastena1606
force-pushed
the
PG-1013-DOC-pg_tde-for-PG17
branch
from
e78b293
to
2818555
Compare
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.
…mpaison