Date: Tue, 21 Jul 2015 11:46:27 +0200 From: Baptiste Daroussin <bapt@FreeBSD.org> To: pgsql@FreeBSD.org, ports@FreeBSD.org Subject: Proposal to fix postgresql package maintainance nightmare Message-ID: <20150721094627.GD21594@ivaldir.etoilebsd.net>
next in thread | raw e-mail | index | archive | help
--k4f25fnPtRuIRUb3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi, We do manage a bunch of postgresql servers on FreeBSD, and I really find the current model of packages postgresql is a nightmare on FreeBSD. Let's first start with the current issues. - Impossible to have tools from both old and new version at the same time (which is necessary to upgrade db and prepare upgrades of db) - Impossible to chose the version we want to run in production without having to rebuild the packages and the whole ports tree with a specific default. - Nightmare each time a new default version is set in the ports tree. Here is my proposal to fix that. Having one single postgresql-client package always on the latest stable version (backward compability being very good) providing the client cli tools and the libraries (those libraries will be used for everything in the ports tree needing to talk to postgresql) Have one full postgresql package per supported version upstream self installing itself into let's say: /usr/local/postgresql94 and symlinks all the client tools to /usr/local/bin suffixed by the version psql94 pg_bla94 etc. That way everything talk to pgsql will only depend on one postgresql-client packages that will smoothly be upgraded to newer versions. All database administrators will have the ability to chose the production version they do want without having to worry about a default version. They can install multiple version in parallel and deal with upgrade the way they want having access to both versions of the tools of the same time. Any opinion on that change? Any idea one how to make the upgrade path as transparent as possible for current setup? (beside of course adding an UPDATING entry) Note that the upgrade path will be quite easy a simple pkg upgrade will propose to upgrade postgresql94-server and propose to remove postgresql94-client (which won't be needed anymore) and if anything on the machine is linked to libpq postgresql-client (the new one) will be automatically pulled. Best regards, Bapt --k4f25fnPtRuIRUb3 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlWuFPMACgkQ8kTtMUmk6EwSGACcCk/TrTkLofUzl5TOy6j0Btyu URgAnRDxw3PxsXZfXDzc//S5ULZIWjII =PcSL -----END PGP SIGNATURE----- --k4f25fnPtRuIRUb3--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150721094627.GD21594>