Skip to content

Latest commit

 

History

History
29 lines (19 loc) · 1.26 KB

File metadata and controls

29 lines (19 loc) · 1.26 KB

Version Numbering

Starting with PostgreSQL {{pgversion}}, Percona uses the following format:

MAJOR.MINOR.PATCH

For example:

{{pspgversion}}

Where:

  • MAJOR = The upstream PostgreSQL major version (e.g. 17 → PostgreSQL 17)
  • MINOR = The upstream PostgreSQL release number
  • PATCH = Percona's internal build number (specific to packaging or Percona-only updates)
Release type Version example What changes?
First Percona build 17.0.1 Initial Percona build on upstream 17.0, build #1
Percona-only update 17.0.2 Build #2 on the same upstream 17.0
Upstream patch/feature 17.1.1 Upstream release → MINOR bump to 1, PATCH reset to 1
Next Percona build 17.1.2 Build #2 on upstream 17.1

The above versioning is only applicable to PSP 17.x.x as it is the only Percona forked server. The third digit is always PSP’s build number, never an upstream patch. If you see it go from …1 → …2 this means a PSP-specific update was shipped.

Since PPG 13 to 16 are pure community versions, only the first 2 digits scheme is used for them.

!!! note If you're looking for more information, check the FAQ.