Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PG-1013 Added build comparison table, moved features from index to comparison #280

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

nastena1606
Copy link
Collaborator

…mpaison

Copy link

github-actions bot commented Sep 16, 2024

Performance test results:
Normal queries: 8931
TDE queries: 8720
Percentage: 97%

@nastena1606 nastena1606 added the documentation Improvements or additions to documentation label Sep 18, 2024

The following is planned for future releases of `pg_tde`:

* Logical replication support
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Logical replication of encrypted tables works in Percona Server for PostgreSQL


| 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 |
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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)

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry i'm not following, what should be changed in the current wording?


The following table provides the differences between the builds:

| PostgreSQL Community build | Percona Server for PostgreSQL build <br> (in addition to features included in the PostgreSQL Community build)|
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd duplicate everything we have for Community in Percona column. Having only additional features makes Percona Server looks less capable visually.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done


## 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.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this needs to be clarified to make sure that the user knows which method do we relate to


## Future releases

The following is planned for future releases of `pg_tde`:

* Logical replication support

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

for which method?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants