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 9B430138825 for ; Tue, 11 Nov 2014 06:35:18 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 37DBDE0A63; Tue, 11 Nov 2014 06:35:12 +0000 (UTC) Received: from mail-wg0-f43.google.com (mail-wg0-f43.google.com [74.125.82.43]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id EA77CE0A53 for ; Tue, 11 Nov 2014 06:35:10 +0000 (UTC) Received: by mail-wg0-f43.google.com with SMTP id y10so10863831wgg.2 for ; Mon, 10 Nov 2014 22:35:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:reply-to:to:subject:date:user-agent:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id; bh=e8imOS1pyhrHuJ7HeqyndmsrPX4yT71LlmFNyU/MSCU=; b=0eteBbBYgOMNvspo8h/WAexm7v+t+Z6/4Ac7U3qsXYZQp1s4u0sbQcZWamRT4oW2aK ZWr6Vd7nxkc/D+RC0ieD7M1Zf7jLpLFhBM8ydTxbNqhkaNLRpzrjhUZj4aBrnGhDiK53 BMql9zv2yYUaGfrfu+Pre5GMk5GODvfUc5OBs/ZJ/8v7LYKInE8NZ/h3MguWl02u5rJI GFmDlf66s6uy35BkIhHPglP6fuMAobWjt4aZa/8EwJuyEDufj66ZRBP/aaC5QmUD9Ysb 4oN2XwxW3ArhbDBbLwBwb2rgj9SzfIrLFfL+Mhelq8p03qfFe1rWMia7Kktxc8D4tL1B Tx4w== X-Received: by 10.180.73.173 with SMTP id m13mr37290171wiv.10.1415687709547; Mon, 10 Nov 2014 22:35:09 -0800 (PST) Received: from dell_xps.localnet (230.3.169.217.in-addr.arpa. [217.169.3.230]) by mx.google.com with ESMTPSA id q9sm16149872wix.6.2014.11.10.22.35.07 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 10 Nov 2014 22:35:07 -0800 (PST) From: Mick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] how to upgrade postgresql under gentoo Date: Tue, 11 Nov 2014 06:34:35 +0000 User-Agent: KMail/1.13.7 (Linux/3.16.5-gentoo; KDE/4.12.5; x86_64; ; ) References: <7984.1415617459@ccs.covici.com> <5460B9DA.6080704@gentoo.org> <20739.1415625385@ccs.covici.com> In-Reply-To: <20739.1415625385@ccs.covici.com> 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: multipart/signed; boundary="nextPart4555753.XRVYnXtRAG"; protocol="application/pgp-signature"; micalg=pgp-sha256 Content-Transfer-Encoding: 7bit Message-Id: <201411110635.04300.michaelkintzios@gmail.com> X-Archives-Salt: d71f1c0e-387a-486f-a86b-6addddaf3060 X-Archives-Hash: ede122ba507234041a8462d8eff135ac --nextPart4555753.XRVYnXtRAG Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Monday 10 Nov 2014 13:16:25 covici@ccs.covici.com wrote: > 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. > > >=20 > > > Thanks in advance for any suggestions. > >=20 > > 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. > >=20 > > If your databases are small enough, it's much less stressful, and it > > works for major version bumps as well. > >=20 > > 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. >=20 > Thanks, maybe I will do that next time. You may also want to file a bug? There may be need for a elog pre-emerge=20 message or some such for users to know how to deal with this in a gentoo=20 system without tearing their hair out. =2D-=20 Regards, Mick --nextPart4555753.XRVYnXtRAG Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAABCAAGBQJUYa4YAAoJELAdA+zwE4Yef4oH/1eR3/E53SoruOh2jJ5roXf5 xV+M6Ao7gkJVhkfK7ta6dHHqBAICp10lsYPeEMCsbePITJHUplf61aiHQtmHpb8v fZZEdwRkGs5zKvEAq+EdvqR6qhjQ6cA/zcz4KMoXBqrebfKcmfpI8UJj0kgC0pl1 MeunxCP9su40vaRQ164I6JXu3d6ZMhvIAeeZDmP8H7ltO5+PjmMlR9TQdgo/EDXO 963qnUaAmtYsNCNvfVEG+6W6N0Vf/BdATGPaAPpzkLqnrke8Wtwleup2QFBbifW+ +94VBeguniglJjWSq1FKlNZdZksapcNtIdp56AK95woLuE2YeKhVcg4kYhl1NbM= =6MRc -----END PGP SIGNATURE----- --nextPart4555753.XRVYnXtRAG--