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-1409 Release notes 17.4.1 #775

Merged
merged 4 commits into from
Mar 27, 2025
Merged

PG-1409 Release notes 17.4.1 #775

merged 4 commits into from
Mar 27, 2025

Conversation

nastena1606
Copy link
Contributor

modified: .github/workflows/main.yml
modified: docs/apt.md
modified: docs/contrib.md
modified: docs/enable-extensions.md
modified: docs/release-notes-v17.2.md
new file: docs/release-notes-v17.4.md
modified: docs/release-notes.md
modified: docs/telemetry.md
modified: mkdocs-base.yml
modified: mkdocs-pdf.yml
modified: variables.yml

@@ -8,7 +8,7 @@ This release of Percona Distribution for PostgreSQL is based on Percona Server f

This release fixes [CVE-2025-1094](https://www.postgresql.org/support/security/CVE-2025-1094/), which closed a vulnerability in the `libpq` PostgreSQL client library but introduced a regression related to string handling for non-null terminated strings. The error would be visible based on how a PostgreSQL client implemented this behavior. This regression affects versions 17.3, 16.7, 15.11, 14.16, and 13.19. For this reason, version 17.3 was skipped.

### Updated version of `pg_tde`
### A new version of `pg_tde`

Percona Distribution for PostgreSQL includes the Release Candidate of `pg_tde` extension that brings in Transparent Data Encryption. This version of `pg_tde` provides a bunch of improvements, among which is the redesigned WAL encryption, single-tenancy support, ability to change key provider configuration and more. Learn about these features in the [`pg_tde` release notes :octicons-link-external-16:](https://docs.percona.com/pg-tde/release-notes/rc.html).
Copy link
Collaborator

Choose a reason for hiding this comment

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

I don't like how it sounds now. I mean when I read it, my impression is that single tenancy was not supported before. Meanwhile what has been improved is the ease of use for single tenant use cases.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Also, changes to key provider were possible before as well. What has changed in this version is that they can be done while the database is offline...

Copy link
Collaborator

Choose a reason for hiding this comment

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

lastly, the tde_heap_basic has been marked as deprecated as of the RC release and it will be going away in the GA

Copy link
Contributor Author

Choose a reason for hiding this comment

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

We have the info about tde_heap_basic deprecation in pg_tde release notes, do we need to duplicate it here?

modified:   .github/workflows/main.yml
        modified:   docs/apt.md
        modified:   docs/contrib.md
        modified:   docs/enable-extensions.md
        modified:   docs/release-notes-v17.2.md
        new file:   docs/release-notes-v17.4.md
        modified:   docs/release-notes.md
        modified:   docs/telemetry.md
        modified:   mkdocs-base.yml
        modified:   mkdocs-pdf.yml
        modified:   variables.yml
@nastena1606 nastena1606 force-pushed the PG-1409-Release-notes-17.4.1 branch from 109fb15 to b65bf63 Compare March 27, 2025 16:56
@nastena1606 nastena1606 temporarily deployed to PG-1409-Release-notes-17.4.1 - postgresql-docs-preview-17 PR #775 March 27, 2025 16:56 — with Render Destroyed
@nastena1606 nastena1606 merged commit 07cc267 into 17 Mar 27, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants