Date: Fri, 11 Apr 2014 07:14:18 +0100 From: Matthew Seaman <matthew@FreeBSD.org> To: Dmitry Morozovsky <marck@rinet.ru>, Steven Schlansker <stevenschlansker@gmail.com> Cc: freebsd-pkg@freebsd.org Subject: Re: Installing bacula-server with PostgreSQL 9.2 Message-ID: <5347883A.5060805@FreeBSD.org> In-Reply-To: <alpine.BSF.2.00.1404110318050.5834@woozle.rinet.ru> References: <413DCEA9-DE6D-4834-B9F1-6C08C7BE5F2C@likeness.com> <533CF8EB.7090403@FreeBSD.org> <6534BBBF-4D98-4FCB-A9AC-4564B0373E08@gmail.com> <alpine.BSF.2.00.1404110318050.5834@woozle.rinet.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --xeQJb2bbPoLtGEUA0l0mmK2veRjJe74qp Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 11/04/2014 00:22, Dmitry Morozovsky wrote: > On Thu, 3 Apr 2014, Steven Schlansker wrote: >=20 >>> The dependency on postgresql90 is "baked into" the compiled package, = and >>> it is not possible to use that package with a different version of >>> postgresql. Apart from anything else, any binaries are linked against= >>> the specific ABI versions of shlibs provided by the postgresql client= >>> package. 'pkg set -o' is not an answer in this case, >> >> That?s very unfortunate! I would expect a binary built against libpq = 9.0 >> to work fine when linked with libpq 9.3, but can?t say that I know exa= ctly >> how good PostgreSQL is about binary compatibility. >=20 > The PostgreSQL team is quite straight about it: there's no promises reg= arding=20 > binary compatibility when you're changing important (in PgSQL case, sec= ond=20 > number) version part; hence, whenever you're drifting from N.M to N.M+1= you're=20 > basically forced to to dump/resore or replication. There were some exc= eptions,=20 > but usually you should be ready to set up new server and then migrate y= our=20 > database one way or another... In fact, the Postgresql project has now declared that point releases incrementing the minor (ie. second part) version number will not need a dump/restore any more. So long as you're using PostgreSQL 9.3 or above. Using replication for upgrades means you have to use trigger based replication ie. Slony -- that's the only replication style that allows different versions either end. Unless you're running at least 9.3, where you can upgrade a streaming replication setup without having to stop, upgrade both ends and restart. Even so, this does not affect the library dependencies for the postgresql binaries. The requirement there is minimally that the library ABI version should not change. I don't know what their policy is -- either forwards + backwards ABI compatibility, or (like the FreeBSD project) forwards compatibility, so a program compiled on FreeBSD 9.0 will work on 9.1, 9.2 etc. but one compiled on 9.2 will not necessarily run on 9.0. The pkg(8) system takes a conservative approach and forces you to install exactly the same versions as used for compilation. The new solver in 1.3 may allow some lattitude in this, but we don't have support for dependencies on ranges of version numbers yet. There's a GSoC proposal to implement that which we're waiting on a decision about. Cheers, Matthew --=20 Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey --xeQJb2bbPoLtGEUA0l0mmK2veRjJe74qp Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.20 (Darwin) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQJ8BAEBCgBmBQJTR4g8XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NTNBNjhCOTEzQTRFNkNGM0UxRTEzMjZC QjIzQUY1MThFMUE0MDEzAAoJELsjr1GOGkATf6cQAJbAQqfbypCTylvUq6AtRPGP uUS64CnblaR1+n4EcBcwpPHCWSQAxeZvxHOOQeni4IoRsLUwZKVGK+hiJGvrzZ7R F8eIyZvljQIfesaUjsn4WijBjSnAXnYSyFdMUlcIcuCK23pIIEPnbGBId0kNSHex PNIKAHOC6CduV8ESaTW5PiyRBLB0tCGbrvIwrYFdl2lZfEDSxoFlw/eLKBj15hwv MERTuuObJkLPjTyuIVkHoQkZeVnrFnPVzYkMn/kJwt62ye5Nw+6RcuwvdPuMybq+ qGxPop96CQz4PcD9k7lNo1dOPYDEFOut4k/w3bCIo1SLomqEh4si1rLlcXNkTHAW mej+veAZNyegm9EEH4RRC644mIDQmIhuK0AhvEuC9+VR1kO99r6hJelE8Jq07vbl PlraXHxywcJVxic7Jlre0EKhqoIjYFmjpxJCCHc3UPyNXj3lMDMJRptl3XXJuB5l Yv2lruIRug1JDtpqWy5FHLm7mjF7HblRaw31v1ARXs8H+i9TVrD/f6HW5GoBARI0 wSG0bjWt99dbWoM1VZ5PbbhkEc3i/z+PB76EskyKKjt23SoeJk3I6eSsAxHXxhpZ qNDDO20wHzeH5yDvEmN4N0KtJ7EooTie+cXthYVAEY7prQOHwfZ8n+2YOaIBb8ye VBnVmc3dYNIUpaeRhFNy =XIZl -----END PGP SIGNATURE----- --xeQJb2bbPoLtGEUA0l0mmK2veRjJe74qp--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5347883A.5060805>