[Slackbuilds-users] PostgreSQL versioning scheme

[Eugen Wissner]

Yes, would be a good thing. Now I have to pass PG_VERSION=10 to the
SlackBuild explicitly and if I forget it, the installation is broken.

Am Sonntag, den 17.11.2019, 07:24 +0100 schrieb Andreas Vögele via
SlackBuilds-users:
> 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."
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>