[Slackbuilds-users] PostgreSQL versioning scheme

Dionysis Ntreou yakizarns1 at gmail.com
Sun Nov 17 12:35:35 UTC 2019


Totally missed this

Thanks for letting me know having a read through that at this moment.
I have done the change and works perfectly
Will push soon





On Sun, Nov 17, 2019 at 6:24 AM Andreas Vögele via SlackBuilds-users <
slackbuilds-users at slackbuilds.org> wrote:

> 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/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20191117/72f195d7/attachment.htm>


More information about the SlackBuilds-users mailing list