From 11acaf1d0db7d2ad20bee84da52fa680969aa55f Mon Sep 17 00:00:00 2001 From: Dragos Andriciuc Date: Mon, 30 Mar 2026 11:50:40 +0300 Subject: [PATCH 1/4] PG-2275 - Repository 404 errors and removed versions (15) This PR backports the updates in #933 for PPG 16 and adds the FAQ file. --- docs/faq.md | 18 ++++++++++++++++++ docs/remove-repo-ver.md | 26 ++++++++++++++++++++++++++ docs/troubleshooting.md | 16 +++++++++++----- mkdocs-base.yml | 5 ++++- 4 files changed, 59 insertions(+), 6 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..8f8a84304 --- /dev/null +++ b/docs/faq.md @@ -0,0 +1,18 @@ +# Frequently Asked Questions + +This FAQ answers common questions about using Percona Distribution for PostgreSQL 15. + +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 PG15+ 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) diff --git a/docs/remove-repo-ver.md b/docs/remove-repo-ver.md new file mode 100644 index 000000000..7ab0d5352 --- /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-15.14` with the latest available `ppg-15.x` + +For upgrade instructions, see the [minor upgrade guide](minor-upgrade.md). diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index 136737ff9..5454ff967 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 Distribution for PostgreSQL 15. + +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: @@ -17,7 +23,7 @@ CREATE SCHEMA demo; To ensure all tables end up in your newly created schema, use the following statement ot set the schema: ```sql -CREATE SCHEMA demo; +SET SCHEMA demo; ``` Replace the `demo` name with your value. diff --git a/mkdocs-base.yml b/mkdocs-base.yml index e34860224..e2e52198f 100644 --- a/mkdocs-base.yml +++ b/mkdocs-base.yml @@ -218,7 +218,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.md From 8141c54d9ef154e9292f77aea60bbc331da6a617 Mon Sep 17 00:00:00 2001 From: Dragos Andriciuc Date: Mon, 30 Mar 2026 12:09:56 +0300 Subject: [PATCH 2/4] Enhance link formatting in troubleshooting.md Updated troubleshooting documentation to include a link icon for the GRANT command. --- docs/troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index 5454ff967..1631fbad6 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 48f8945253122892583ae3484aaeeb30d1ad7ec1 Mon Sep 17 00:00:00 2001 From: Dragos Andriciuc Date: Thu, 2 Apr 2026 17:13:24 +0300 Subject: [PATCH 3/4] Update removal reasons and add release notes reference Clarified reasons for repository removal and added reference to release notes. --- 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 7ab0d5352..c3fcb02e1 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-v15.14.md). ## What should you do instead? From eff61e2445908c6dc91fb7ddc4b8979a975ccdae Mon Sep 17 00:00:00 2001 From: Dragos Andriciuc Date: Thu, 2 Apr 2026 17:18:31 +0300 Subject: [PATCH 4/4] Update remove-repo-ver.md --- docs/remove-repo-ver.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/remove-repo-ver.md b/docs/remove-repo-ver.md index c3fcb02e1..b58a4fc3d 100644 --- a/docs/remove-repo-ver.md +++ b/docs/remove-repo-ver.md @@ -15,7 +15,7 @@ These versions were part of a release that included known issues affecting stabi 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-v15.14.md). +For additional details, see the [relevant release notes](release-notes-v15.15.md). ## What should you do instead?