Just a quick status update. My production servers were using
PostgreSQL 16. Last week I updated to PostgreSQL 17. I hope to upgrade
to 18 this or next week. After that I will know for sure that
php84 is compatible and update my slackbuild dependencies.

I understand that it's difficult to maintain that many PostgreSQL
versions, but I still think that it defeats the purpose of PostgreSQL
having long-term support for their major releases to switch to each
new major release. Switching to the new major release is not a simple
"upgradepkg"; I need to rebuild my replica data each time for example.

Having said that, thanks for the excellent PostgreSQL support for
Slackware.

Regards
Eugen

On Sun Jul 5, 2026 at 3:03 AM CEST, B. Watson wrote:
>
> To everyone who has scripts with REQUIRES="postgresql"...
>
> We already have 4 newer versions of postgresql in the repo,
> postgresql15 through postgresql18. Please test your scripts against
> these versions, and get them working with the highest-numbered version
> of postgresql possible. Most likely, most of these will work fine
> without patching/etc, but there's no way to find out until you try it.
>
> postgresql 14.x is going to be EOLed upstream in November of this
> year, and we plan to remove it from our repo. That's about 90 days
> from now, which hopefully gives enough time for getting things to work
> with a newer postgresql.
>
> At the same time, we'd like to remove postgresql15, postgresql16, and
> postgresql17 if possible (if nothing ends up requiring them). Ideally,
> all dependees should be updated to work with postgresql18 (which may
> mean updating the dependees' versions, too).
>
> Affected builds and maintainers:
>
> PyGreSQL  (Christoph Willing <[email protected]>)
> barman  (Dimitris Zlatanidis <[email protected]>)
> cyphesis  (Dimitris Zlatanidis <[email protected]>)
> dovecot-pgsql  (Eugene Wissner <[email protected]>)
> geopandas  (ArTourter <[email protected]>)
> grass  (Christoph Willing <[email protected]>)
> libpqxx  (Benjamin Trigona-Harany <[email protected]>)
> odoo  (Fernando Lopez Jr. <[email protected]>)
> osm2pgsql  (Giancarlo Dessi <[email protected]>)
> osm2pgsql-legacy  (Giancarlo Dessi <[email protected]>)
> pcp  (Lockywolf <[email protected]>)
> pd-psql  (Michales Michaloudes <[email protected]>)
> pdal  (Giancarlo Dessi <[email protected]>)
> perl-DBD-Pg  (Kevin Bryant <[email protected]>)
> pgmodeler  (Joielechong <[email protected]>)
> pgpool-II  (Dejan Strbac <[email protected]>)
> pgrouting  (Giancarlo Dessi <[email protected]>)
> pgsanity  (Yth - Arnaud <[email protected]>)
> pgtcl-ng  (Richard Ellis <[email protected]>)
> php-pgsql  (Heinz Wiesinger <[email protected]>)
> php82  (Eugene Wissner <[email protected]>)
> php84  (Eugene Wissner <[email protected]>)
> phppgadmin  (Michel A. Begue <[email protected]>)
> postfix-pgsql  (Eugene Wissner <[email protected]>)
> postgis  (Giancarlo Dessi <[email protected]>)
> psqlodbc  (Chris Walker <[email protected]>)
> python3-psycopg2  (Yth - Arnaud <[email protected]>)
> python3-psycopg3  (Zlatanidis Dimitris <[email protected]>)
> qgis  (Giancarlo Dessi <[email protected]>)
> qt5-postgresql  (Heinz Wiesinger <[email protected]>)
> virtualpg  (Konrad J Hambrick <[email protected]>)
> _______________________________________________
> SlackBuilds-users mailing list
> [email protected]
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/

_______________________________________________
SlackBuilds-users mailing list
[email protected]
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Reply via email to