[Slackbuilds-users] PostgreSQL versioning scheme

Willy Sudiarto Raharjo willysr at slackbuilds.org
Sun Nov 17 10:26:29 UTC 2019

> PostgreSQL changed its versioning scheme with version 10. See
> https://www.postgresql.org/about/news/1786/ and
> https://en.wikipedia.org/wiki/PostgreSQL#Release_history
> Shouldn't PG_VERSION in system/postgresql.SlackBuild be just "10" in
> order to simplify updates?
> According to https://www.postgresql.org/docs/10/upgrading.html cluster
> upgrades are not required for minor releases.
> "Minor releases never change the internal storage format and are always
> compatible with earlier and later minor releases of the same major
> version number. For example, version 10.1 is compatible with version
> 10.0 and version 10.6. [...] To update between compatible versions, you
> simply replace the executables while the server is down and restart the
> server. The data directory remains unchanged — minor upgrades are that
> simple."

I CC the maintainer just in case he didn't follow the list yet

Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20191117/a5d8bd9b/attachment-0001.asc>

More information about the SlackBuilds-users mailing list