Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Added the extras repository and a diagram #579

Open
wants to merge 1 commit into
base: 16
Choose a base branch
from
Open

Added the extras repository and a diagram #579

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file added docs/_images/diagrams/PG-repo-choice.png
View file
Open in desktop
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
19 changes: 15 additions & 4 deletions docs/repo-overview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,13 +1,17 @@
# Repositories overview

Percona provides two repositories for Percona Distribution for PostgreSQL.
Percona provides the following repositories for Percona Distribution for PostgreSQL.

| Major release repository | Minor release repository |
| ------------------------ | ------------------------ |
| *Major Release repository* (`ppg-16`) it includes the latest version packages. Whenever a package is updated, the package manager of your operating system detects that and prompts you to update. As long as you update all Distribution packages at the same time, you can ensure that the packages you’re using have been tested and verified by Percona. <br><br> We recommend installing Percona Distribution for PostgreSQL from the *Major Release repository*| *Minor Release repository* includes a particular minor release of the database and all of the packages that were tested and verified to work with that minor release (e.g. `ppg-16.0`). You may choose to install Percona Distribution for PostgreSQL from the Minor Release repository if you have decided to standardize on a particular release which has passed rigorous testing procedures and which has been verified to work with your applications. This allows you to deploy to a new host and ensure that you’ll be using the same version of all the Distribution packages, even if newer releases exist in other repositories. <br> <br> The disadvantage of using a Minor Release repository is that you are locked in this particular release. When potentially critical fixes are released in a later minor version of the database, you will not be prompted for an upgrade by the package manager of your operating system. You would need to change the configured repository in order to install the upgrade.|
![Repository choice](_images/diagrams/PG-repo-choice.png)

| Major release repository | Minor release repository | Extras repository |
| ------------------------ | ------------------------ | ----------------- |
| *Major Release repository* (`ppg-16`) it includes the latest version packages. Whenever a package is updated, the package manager of your operating system detects that and prompts you to update. As long as you update all Distribution packages at the same time, you can ensure that the packages you’re using have been tested and verified by Percona. <br><br> We recommend installing Percona Distribution for PostgreSQL from the *Major Release repository*| *Minor Release repository* includes a particular minor release of the database and all of the packages that were tested and verified to work with that minor release (e.g. `ppg-16.0`). You may choose to install Percona Distribution for PostgreSQL from the Minor Release repository if you have decided to standardize on a particular release which has passed rigorous testing procedures and which has been verified to work with your applications. This allows you to deploy to a new host and ensure that you’ll be using the same version of all the Distribution packages, even if newer releases exist in other repositories. <br> <br> The disadvantage of using a Minor Release repository is that you are locked in this particular release. When potentially critical fixes are released in a later minor version of the database, you will not be prompted for an upgrade by the package manager of your operating system. You would need to change the configured repository in order to install the upgrade. | The *Extras* repository (e.g. `ppg-16-extras`) includes modules, extensions and libraries not included in Percona Distribution for PostgreSQL but verified to be compatible with it. The components in the Extras repository are always built only against the latest minor version of the latest major version of PostgreSQL. With the release of the next major version (e.g. 17), the update of the previous major version (e.g.16) stops. <br><br> The aim of the Extras repository is to make its modules, extensions and libraries available for community users as soon as possible and gather their feedback on using those modules. |

## Repository contents

### Major / minor repositories

Percona Distribution for PostgreSQL provides individual packages for its components. It also includes two meta-packages: `percona-ppg-server` and `percona-ppg-server-ha`.

Using a meta-package, you can install all components it contains in one go.
Expand Down Expand Up @@ -56,6 +60,13 @@ The `percona-ppg-server-ha` meta-package installs high-availability components t
| `etcd-client`, `etcd-server` | The client/server of the distributed key-value store. [^2]|


### Extras repository

| Package contents | Description |
| ---------------- | --------------------------------------- |
| | |



[^1]: Is included in repositories for RHEL 8 / CentOS 8 operating systems
[^2]: Are included in repositories for Debian 12 operating system