Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VfxSH-0000Hr-MB for pgsql-admin@arkaria.postgresql.org; Mon, 11 Nov 2013 19:47:25 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1VfxSH-00053F-19 for pgsql-admin@arkaria.postgresql.org; Mon, 11 Nov 2013 19:47:25 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VfxSG-000533-6o for pgsql-admin@postgresql.org; Mon, 11 Nov 2013 19:47:24 +0000 Received: from mail-gg0-x231.google.com ([2607:f8b0:4002:c02::231]) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VfxS8-00009B-Tz for pgsql-admin@postgresql.org; Mon, 11 Nov 2013 19:47:23 +0000 Received: by mail-gg0-f177.google.com with SMTP id n3so6874ggf.36 for ; Mon, 11 Nov 2013 11:47:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:reply-to:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=lnNWVhQl8YG+aA1pQ9rBdXTe2A9o678Ketg1KI/d+rU=; b=dY4baaCMFq7k1YaG/rfkurkW8ovTdZ3QokzzU42Dsq/QjTlmPnLev3HPPHGmm8vSGU xj0m8jSIj3YPX83Ciz7KcT5gmpFhxA3dOdj1tZxxzVFNPCPmHftI6ZhufsciD25u0TDf PDTdkqXnIIRrmdreXoRDIevPy+AOvQLUApcPUvTDyeT2RGP/8e9dxOK3sa9R0kfAU3dx nkODNAsXqNvUDXll1HKZxwUB8LDt+nScYYrQy7zdSCkupTBVxQNi2vavSLHNYQC6aldD MQTa/KyproNAfhYPilP7aXtS3D/BBXhDBdw8csIgs0yeBi+7+p+CkGHsXiCwNgSyXe24 x5QA== X-Received: by 10.236.105.164 with SMTP id k24mr12662140yhg.30.1384199234151; Mon, 11 Nov 2013 11:47:14 -0800 (PST) Received: from [192.169.100.54] (106-139-89-200.fibertel.com.ar. [200.89.139.106]) by mx.google.com with ESMTPSA id m68sm41487199yhj.22.2013.11.11.11.47.11 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 11 Nov 2013 11:47:13 -0800 (PST) Message-ID: <5281343C.1060901@pasteleros.org.ar> Date: Mon, 11 Nov 2013 16:47:08 -0300 From: Alejandro Brust Reply-To: alejandrob@pasteleros.org.ar User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130503 Thunderbird/17.0.5 MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Re: using pg_upgrade on FreeBSD for postgresql installed by ports References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Pg-Spam-Score: -2.0 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org Hello I recommend you to install the new version in other directory (start the cluster on other port.... first) and perform the backup with de "NEW" client. Restore the backup(with de "NEW" client), test...and test...and compare. Then U could promote the new one version to production. Hope it help El 11/11/2013 13:42, Luca Ferrari escribió: > Hi all, > is there any best practice in using pg_upgrade to upgrade a cluster > installed using ports on FreeBSD? I mean, the port will install the > binaries over the previous installation therefore removing the old > binaries. May be using the "working" directory before the port get > installed? > > Thanks, > Luca > > -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin