Skip to content

Commit 6ee6b4c

Browse files
authored
PG-2275 - Repository 404 errors and removed versions (15) (#935)
This PR backports the updates in #933 for PPG 15 and adds the FAQ file.
1 parent cab771e commit 6ee6b4c

4 files changed

Lines changed: 61 additions & 6 deletions

File tree

docs/faq.md

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
# Frequently Asked Questions
2+
3+
This FAQ answers common questions about using Percona Distribution for PostgreSQL 15.
4+
5+
If you're looking for help with errors or runtime issues, see the [Troubleshooting guide](troubleshooting.md).
6+
7+
## Does MINOR cover both upstream feature and patch releases?
8+
9+
Yes, if we ship a future minor of PG15+ this always includes the patchset from Percona as well.
10+
11+
## When upstream bumps MINOR, should PATCH always reset to 1?
12+
13+
The first release will always be `MAJOR.MINOR.1`.
14+
15+
!!! note
16+
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.
17+
18+
[**Get help from Percona**](get-help.md)

docs/remove-repo-ver.md

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
# Repository 404 errors and removed versions
2+
3+
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.
4+
5+
The following versions are affected:
6+
7+
- `ppg-14.19`
8+
- `ppg-15.14`
9+
- `ppg-16.10`
10+
- `ppg-17.6`
11+
12+
## Reason for removal
13+
14+
These versions were part of a release that included known issues affecting stability and reliability.
15+
16+
To prevent unintended usage, these repositories were removed from distribution. These versions are not recommended for production use.
17+
18+
For additional details, see the [relevant release notes](release-notes-v15.15.md).
19+
20+
## What should you do instead?
21+
22+
Use the latest available minor version for your PostgreSQL major version.
23+
24+
Examples:
25+
26+
- Replace `ppg-15.14` with the latest available `ppg-15.x`
27+
28+
For upgrade instructions, see the [minor upgrade guide](minor-upgrade.md).

docs/troubleshooting.md

Lines changed: 11 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,18 @@
1-
# Troubleshooting guide
1+
# Troubleshooting guide overview
22

3-
## Cannot create a table. Permission denied in schema `public`
3+
This guide helps you identify and resolve common issues when installing, configuring, or running Percona Distribution for PostgreSQL 15.
4+
5+
If you're looking for general information or usage tips, check the [FAQ](faq.md).
6+
7+
## Common issues
8+
9+
### Cannot create a table. Permission denied in schema `public`
410

511
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.
612

7-
When you create a table without specifying a schema name, it ends up in the `public` schema by default.
13+
When you create a table without specifying a schema name, it ends up in the `public` schema by default.
814

9-
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.
15+
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.
1016

1117
To create a schema, use the following statement:
1218

@@ -17,7 +23,7 @@ CREATE SCHEMA demo;
1723
To ensure all tables end up in your newly created schema, use the following statement ot set the schema:
1824

1925
```sql
20-
CREATE SCHEMA demo;
26+
SET SCHEMA demo;
2127
```
2228

2329
Replace the `demo` name with your value.

mkdocs-base.yml

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -218,7 +218,10 @@ nav:
218218
- "Major upgrade": major-upgrade.md
219219
- minor-upgrade.md
220220
- migration.md
221-
- Troubleshooting guide: troubleshooting.md
221+
- FAQ: faq.md
222+
- Troubleshooting guide:
223+
- "Overview": troubleshooting.md
224+
- "Repository 404 errors and removed versions": remove-repo-ver.md
222225
- Uninstall: uninstalling.md
223226
- Release notes:
224227
- "Release notes index": release-notes.md

0 commit comments

Comments
 (0)