From owner-freebsd-pkg@FreeBSD.ORG Thu Apr 10 23:25:47 2014 Return-Path: Delivered-To: freebsd-pkg@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6948A3E8; Thu, 10 Apr 2014 23:25:47 +0000 (UTC) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D533A11DA; Thu, 10 Apr 2014 23:25:46 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.14.5/8.14.5) with ESMTP id s3ANMc9O030759; Fri, 11 Apr 2014 03:22:38 +0400 (MSK) (envelope-from marck@rinet.ru) Date: Fri, 11 Apr 2014 03:22:38 +0400 (MSK) From: Dmitry Morozovsky To: Steven Schlansker Subject: Re: Installing bacula-server with PostgreSQL 9.2 In-Reply-To: <6534BBBF-4D98-4FCB-A9AC-4564B0373E08@gmail.com> Message-ID: References: <413DCEA9-DE6D-4834-B9F1-6C08C7BE5F2C@likeness.com> <533CF8EB.7090403@FreeBSD.org> <6534BBBF-4D98-4FCB-A9AC-4564B0373E08@gmail.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) X-NCC-RegID: ru.rinet X-OpenPGP-Key-ID: 6B691B03 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (woozle.rinet.ru [0.0.0.0]); Fri, 11 Apr 2014 03:22:39 +0400 (MSK) Cc: Matthew Seaman , freebsd-pkg@freebsd.org X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Apr 2014 23:25:47 -0000 On Thu, 3 Apr 2014, Steven Schlansker wrote: > > 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 exactly > how good PostgreSQL is about binary compatibility. The PostgreSQL team is quite straight about it: there's no promises regarding binary compatibility when you're changing important (in PgSQL case, second number) version part; hence, whenever you're drifting from N.M to N.M+1 you're basically forced to to dump/resore or replication. There were some exceptions, but usually you should be ready to set up new server and then migrate your database one way or another... -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: marck@FreeBSD.org ] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------