From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id CB2AA138825 for ; Mon, 10 Nov 2014 13:16:34 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 080B2E096A; Mon, 10 Nov 2014 13:16:29 +0000 (UTC) Received: from mail0200.smtp25.com (mail0200.smtp25.com [174.37.170.200]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id AE207E0946 for ; Mon, 10 Nov 2014 13:16:27 +0000 (UTC) Received: from ccs.covici.com (s-out-001.smtp25.com [67.228.91.90]) by s-out-001.smtp25.com (8.14.2/8.14.2) with ESMTP id sAADGPSh029925 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Mon, 10 Nov 2014 08:16:26 -0500 Received: from ccs.covici.com (localhost [127.0.0.1]) by ccs.covici.com (8.14.9/8.14.8) with ESMTP id sAADGPoA020742 for ; Mon, 10 Nov 2014 08:16:25 -0500 From: covici@ccs.covici.com To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] how to upgrade postgresql under gentoo In-reply-to: <5460B9DA.6080704@gentoo.org> References: <7984.1415617459@ccs.covici.com> <5460B9DA.6080704@gentoo.org> Comments: In-reply-to Michael Orlitzky message dated "Mon, 10 Nov 2014 08:12:58 -0500." X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.4.1 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <20738.1415625384.1@ccs.covici.com> Date: Mon, 10 Nov 2014 08:16:25 -0500 Message-ID: <20739.1415625385@ccs.covici.com> X-SpamH-OriginatingIP: 70.109.53.110 X-SpamH-Filter: s-out-001.smtp25.com-sAADGPSh029925 X-Archives-Salt: f0fc6e4a-8557-4233-a7ea-812d055f2a91 X-Archives-Hash: 40b6deacb8f2e87b606cbe3c5f855569 Michael Orlitzky wrote: > On 11/10/2014 06:04 AM, covici@ccs.covici.com wrote: > > Hi. I have a puzzle regarding upgrading postgresql. In my recent world > > update I went from 9.4_beta2 to beta3, but when I tried to start the > > server, it complained that the databases were written with a different > > "catalog version" -- whatever that is, and the pg_upgrade tool requires > > both old and new binaries to actually upgrade the database. So as a > > temporary measure, I went back to beta2 and things worked again. So > > what the heck are you supposed to do here, I like pg, but this is very > > strange to me. > > > > Thanks in advance for any suggestions. > > > > pg_upgrade has always been a PITA for me. There's an easier way that > always works: run pg_dumpall, upgrade postgres, and then restore the > dump file. > > If your databases are small enough, it's much less stressful, and it > works for major version bumps as well. > > If you're worried about overwriting your data, you could always back up > the beta2 binary files, and then create empty databases under beta3 > before restoring. Thanks, maybe I will do that next time. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici covici@ccs.covici.com