From 045592dbdb176be2f0b28fc8454a8611581cc868 Mon Sep 17 00:00:00 2001 From: Dragos Andriciuc Date: Wed, 20 May 2026 11:37:51 +0300 Subject: [PATCH 1/3] PG-2384 - Add pg_tde warning note to use pg_tde_upgrade This PR adds a warning note informing the user they need to use pg_tde_upgrade instead of pg_upgrade in their distribution in case pg_tde is used to encrypt the cluster. --- docs/major-upgrade.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/major-upgrade.md b/docs/major-upgrade.md index 9712f3328..b64eb14b2 100644 --- a/docs/major-upgrade.md +++ b/docs/major-upgrade.md @@ -10,7 +10,10 @@ To ensure a smooth upgrade path, follow these steps: !!! note When running a major upgrade on **RHEL 8 and compatible derivatives**, consider the following: - Percona Distribution for PostgreSQL 16.3, 15.7, 14.12, 13.15 and 12.18 include `llvm` packages 16.0.6, while its previous versions 16.2, 15.6, 14.11, 13.14, and 12.17 include `llvm` 12.0.1. Since `llvm` libraries differ and are not compatible, the direct major version upgrade from 15.6 to 16.3 may cause issues. + Percona Distribution for PostgreSQL 16.3, 15.7, 14.12, 13.15 and 12.18 include `llvm` packages 16.0.6, while its previous versions 16.2, 15.6, 14.11, 13.14, and 12.17 include `llvm` 12.0.1. Since `llvm` libraries differ and are not compatible, the direct major version upgrade from 15.6 to 16.3 may cause issues. + +!!! warning + If your cluster uses `pg_tde`, you **must** use `pg_tde_upgrade` instead of `pg_upgrade`. Using `pg_upgrade` on an encrypted cluster is not supported and will result in data corruption. The server may start successfully but queries against encrypted tables will fail. The in-place upgrade means installing a new version without removing the old version and keeping the data files on the server. From e3748c70392a85645053f898876158ddf5a0282a Mon Sep 17 00:00:00 2001 From: Dragos Andriciuc Date: Wed, 20 May 2026 11:47:03 +0300 Subject: [PATCH 2/3] Enhance pg_tde warning with external link Updated warning to include a link for pg_tde_upgrade. --- docs/major-upgrade.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/major-upgrade.md b/docs/major-upgrade.md index b64eb14b2..e9b57f036 100644 --- a/docs/major-upgrade.md +++ b/docs/major-upgrade.md @@ -13,7 +13,7 @@ To ensure a smooth upgrade path, follow these steps: Percona Distribution for PostgreSQL 16.3, 15.7, 14.12, 13.15 and 12.18 include `llvm` packages 16.0.6, while its previous versions 16.2, 15.6, 14.11, 13.14, and 12.17 include `llvm` 12.0.1. Since `llvm` libraries differ and are not compatible, the direct major version upgrade from 15.6 to 16.3 may cause issues. !!! warning - If your cluster uses `pg_tde`, you **must** use `pg_tde_upgrade` instead of `pg_upgrade`. Using `pg_upgrade` on an encrypted cluster is not supported and will result in data corruption. The server may start successfully but queries against encrypted tables will fail. + If your cluster uses `pg_tde`, you **must** use [`pg_tde_upgrade` :octicons-link-external-16:](https://docs.percona.com/pg-tde/command-line-tools/pg-tde-upgrade.html) instead of `pg_upgrade`. Using `pg_upgrade` on an encrypted cluster is not supported and will result in data corruption. The server may start successfully but queries against encrypted tables will fail. The in-place upgrade means installing a new version without removing the old version and keeping the data files on the server. From 08498ef814b1b0b3305694496d7d95517de1c1ed Mon Sep 17 00:00:00 2001 From: Dragos Andriciuc Date: Wed, 20 May 2026 16:07:29 +0300 Subject: [PATCH 3/3] Update major-upgrade.md --- docs/major-upgrade.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/major-upgrade.md b/docs/major-upgrade.md index e9b57f036..dc9544540 100644 --- a/docs/major-upgrade.md +++ b/docs/major-upgrade.md @@ -13,7 +13,7 @@ To ensure a smooth upgrade path, follow these steps: Percona Distribution for PostgreSQL 16.3, 15.7, 14.12, 13.15 and 12.18 include `llvm` packages 16.0.6, while its previous versions 16.2, 15.6, 14.11, 13.14, and 12.17 include `llvm` 12.0.1. Since `llvm` libraries differ and are not compatible, the direct major version upgrade from 15.6 to 16.3 may cause issues. !!! warning - If your cluster uses `pg_tde`, you **must** use [`pg_tde_upgrade` :octicons-link-external-16:](https://docs.percona.com/pg-tde/command-line-tools/pg-tde-upgrade.html) instead of `pg_upgrade`. Using `pg_upgrade` on an encrypted cluster is not supported and will result in data corruption. The server may start successfully but queries against encrypted tables will fail. + When doing a major version upgrade, if your cluster uses `pg_tde`, you **must** use [`pg_tde_upgrade` :octicons-link-external-16:](https://docs.percona.com/pg-tde/command-line-tools/pg-tde-upgrade.html) instead of `pg_upgrade`. Using `pg_upgrade` on an encrypted cluster is not supported and will result in data corruption. The server may start successfully but queries against encrypted tables will fail. The in-place upgrade means installing a new version without removing the old version and keeping the data files on the server.