PG-2275 - Repository 404 errors and removed versions (16)

This PR backports the updates in #933 for PPG 16.

Author: Andriciuc

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)

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

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:
 

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