From f50cd7b0e39c00a4f130151ad87f41f458a426ad Mon Sep 17 00:00:00 2001 From: Dragos Andriciuc Date: Mon, 30 Mar 2026 11:37:55 +0300 Subject: [PATCH 1/5] PG-2275 - Repository 404 errors and removed versions (16) This PR backports the updates in #933 for PPG 16. --- docs/faq.md | 18 ++++++++++++++++++ docs/remove-repo-ver.md | 26 ++++++++++++++++++++++++++ docs/troubleshooting.md | 14 ++++++++++---- mkdocs.yml | 5 ++++- 4 files changed, 58 insertions(+), 5 deletions(-) create mode 100644 docs/faq.md create mode 100644 docs/remove-repo-ver.md diff --git a/docs/faq.md b/docs/faq.md new file mode 100644 index 000000000..478b6cfc0 --- /dev/null +++ b/docs/faq.md @@ -0,0 +1,18 @@ +# Frequently Asked Questions + +This FAQ answers common questions about using Percona Distribution for PostgreSQL 16. + +If you're looking for help with errors or runtime issues, see the [Troubleshooting guide](troubleshooting.md). + +## Does MINOR cover both upstream feature and patch releases? + +Yes, if we ship a future minor of PG17+ this always includes the patchset from Percona as well. + +## When upstream bumps MINOR, should PATCH always reset to 1? + +The first release will always be `MAJOR.MINOR.1`. + +!!! note + Don’t see your question here? Feel free to click the link below to get free database assistance or contact our experts for personalized support. + + [**Get help from Percona**](get-help.md) \ No newline at end of file diff --git a/docs/remove-repo-ver.md b/docs/remove-repo-ver.md new file mode 100644 index 000000000..05346be5f --- /dev/null +++ b/docs/remove-repo-ver.md @@ -0,0 +1,26 @@ +# Repository 404 errors and removed versions + +Some Percona Distribution for PostgreSQL repository versions are no longer available and may return a `404 Not Found` error when accessed. This happens because these versions have been removed from the repository. + +The following versions are affected: + +- `ppg-14.19` +- `ppg-15.14` +- `ppg-16.10` +- `ppg-17.6` + +## Reason for removal + +To prevent unintended usage, these repositories were removed from distribution. + +These versions are not recommended for production use. + +## What should you do instead? + +Use the latest available minor version for your PostgreSQL major version. + +Examples: + +- Replace `ppg-16.10` with the latest available `ppg-16.x` + +For upgrade instructions, see the [minor upgrade guide](minor-upgrade.md). diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index 9663c2fe8..115f1ff86 100644 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md @@ -1,12 +1,18 @@ -# Troubleshooting guide +# Troubleshooting guide overview -## Cannot create a table. Permission denied in schema `public` +This guide helps you identify and resolve common issues when installing, configuring, or running Percona Server for PostgreSQL 17. + +If you're looking for general information or usage tips, check the [FAQ](faq.md). + +## Common issues + +### Cannot create a table. Permission denied in schema `public` Every database in PostgreSQL has a default schema called `public`. A schema stores database objects like tables, views, indexes and allows organizing them into logical groups. -When you create a table without specifying a schema name, it ends up in the `public` schema by default. +When you create a table without specifying a schema name, it ends up in the `public` schema by default. -Starting with PostgreSQL 15, non-database owners cannot access the `public` schema. Therefore, you can either grant privileges to the database for your user using the [GRANT](https://www.postgresql.org/docs/{{pgvesrion}}/sql-grant.html) command or create your own schema to insert the data. +Starting with PostgreSQL 15, non-database owners cannot access the `public` schema. Therefore, you can either grant privileges to the database for your user using the [GRANT](https://www.postgresql.org/docs/{{pgversion}}/sql-grant.html) command or create your own schema to insert the data. To create a schema, use the following statement: diff --git a/mkdocs.yml b/mkdocs.yml index fc02a3d6a..e28249095 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -67,7 +67,10 @@ nav: - "Major upgrade": major-upgrade.md - minor-upgrade.md - migration.md - - Troubleshooting guide: troubleshooting.md + - FAQ: faq.md + - Troubleshooting guide: + - "Overview": troubleshooting.md + - "Repository 404 errors and removed versions": remove-repo-ver.md - Uninstall: uninstalling.md - Release notes: - "Release notes index": release-notes/release-notes.md From 066e58a63b983e18ebad42b1e4354588c291d3f2 Mon Sep 17 00:00:00 2001 From: Dragos Andriciuc Date: Mon, 30 Mar 2026 11:48:34 +0300 Subject: [PATCH 2/5] Update troubleshooting.md --- docs/troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index 115f1ff86..72809c368 100644 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md @@ -1,6 +1,6 @@ # Troubleshooting guide overview -This guide helps you identify and resolve common issues when installing, configuring, or running Percona Server for PostgreSQL 17. +This guide helps you identify and resolve common issues when installing, configuring, or running Percona Distribution for PostgreSQL 16. If you're looking for general information or usage tips, check the [FAQ](faq.md). From a8f8486d21ae756321ffed038bf463399ea27256 Mon Sep 17 00:00:00 2001 From: Dragos Andriciuc Date: Mon, 30 Mar 2026 11:49:05 +0300 Subject: [PATCH 3/5] Fix version reference in FAQ about MINOR releases Corrected the version reference from PG17 to PG16 in the FAQ. --- docs/faq.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/faq.md b/docs/faq.md index 478b6cfc0..f06004402 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -6,7 +6,7 @@ If you're looking for help with errors or runtime issues, see the [Troubleshooti ## Does MINOR cover both upstream feature and patch releases? -Yes, if we ship a future minor of PG17+ this always includes the patchset from Percona as well. +Yes, if we ship a future minor of PG16+ this always includes the patchset from Percona as well. ## When upstream bumps MINOR, should PATCH always reset to 1? @@ -15,4 +15,4 @@ The first release will always be `MAJOR.MINOR.1`. !!! note Don’t see your question here? Feel free to click the link below to get free database assistance or contact our experts for personalized support. - [**Get help from Percona**](get-help.md) \ No newline at end of file + [**Get help from Percona**](get-help.md) From 62ebdc5ff99bddbc1e618fc73398541c126e1042 Mon Sep 17 00:00:00 2001 From: Dragos Andriciuc Date: Mon, 30 Mar 2026 12:09:19 +0300 Subject: [PATCH 4/5] Update troubleshooting.md --- docs/troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index 72809c368..ae1a94258 100644 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md @@ -12,7 +12,7 @@ Every database in PostgreSQL has a default schema called `public`. A schema stor When you create a table without specifying a schema name, it ends up in the `public` schema by default. -Starting with PostgreSQL 15, non-database owners cannot access the `public` schema. Therefore, you can either grant privileges to the database for your user using the [GRANT](https://www.postgresql.org/docs/{{pgversion}}/sql-grant.html) command or create your own schema to insert the data. +Starting with PostgreSQL 15, non-database owners cannot access the `public` schema. Therefore, you can either grant privileges to the database for your user using the [GRANT :octicons-link-external-16:](https://www.postgresql.org/docs/{{pgversion}}/sql-grant.html) command or create your own schema to insert the data. To create a schema, use the following statement: From 6e220f66bdb3d1fc3d0ffc264fe65e0f149eb61b Mon Sep 17 00:00:00 2001 From: Dragos Andriciuc Date: Thu, 2 Apr 2026 17:24:19 +0300 Subject: [PATCH 5/5] Update remove-repo-ver.md --- docs/remove-repo-ver.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/remove-repo-ver.md b/docs/remove-repo-ver.md index 05346be5f..b94bbf607 100644 --- a/docs/remove-repo-ver.md +++ b/docs/remove-repo-ver.md @@ -11,9 +11,11 @@ The following versions are affected: ## Reason for removal -To prevent unintended usage, these repositories were removed from distribution. +These versions were part of a release that included known issues affecting stability and reliability. -These versions are not recommended for production use. +To prevent unintended usage, these repositories were removed from distribution. These versions are not recommended for production use. + +For additional details, see the [relevant release notes](release-notes/release-notes-v16.11.md). ## What should you do instead?