From owner-freebsd-ports@FreeBSD.ORG Tue Dec 16 11:36:17 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C44A41A6A for ; Tue, 16 Dec 2014 11:36:17 +0000 (UTC) Received: from gw.zefyris.com (sabik.zefyris.com [IPv6:2001:7a8:3c67:2::254]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5C31313A4 for ; Tue, 16 Dec 2014 11:36:17 +0000 (UTC) Received: from sekishi.zefyris.com (sekishi.zefyris.com [IPv6:2001:7a8:3c67:2::12]) by gw.zefyris.com (8.14.5/8.14.5) with ESMTP id sBGApEKf402349; Tue, 16 Dec 2014 11:51:15 +0100 (CET) Date: Tue, 16 Dec 2014 11:51:14 +0100 From: Francois Tigeot To: freebsd-ports@freebsd.org Subject: Re: Discrepancy in postgresql entry in UPDATING Message-ID: <20141216105114.GB379084@sekishi.zefyris.com> References: <548F8DCA.8070407@bluerosetech.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <548F8DCA.8070407@bluerosetech.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (gw.zefyris.com [IPv6:2001:7a8:3c67:2::254]); Tue, 16 Dec 2014 11:51:16 +0100 (CET) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Dec 2014 11:36:17 -0000 On Mon, Dec 15, 2014 at 05:41:30PM -0800, Darren Pilgrim wrote: > The entry reads: > > 20141208: [...] > When using binary packages, if you only use the client port, you can > issue the following command to follow the default version: > > # pkg set -o databases/postgresql92-client:databases/postgresql93-client > > The problem is pg_upgrade requires both the old and new versions be > installed concurrently--something pkg/ports can't do. So how are we > supposed to upgrade? With pg_upgrade, I found the best method to be: - locally build the two postgres versions you're interested in from the Postgres distfiles. - run pg_upgrade from one of them and don't bother with the packages. The Postgres packages are fine for regular operation but like you said, not really adapted for this kind of one shot operation IMHO. -- Francois Tigeot