Received: from localhost (unknown [200.46.204.191])
	by postgresql.org (Postfix) with ESMTP id EB6D72E157F
	for <pgsql-advocacy-postgresql.org@postgresql.org>;
	Tue, 13 Nov 2007 11:56:06 -0400 (AST)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024)
	with ESMTP id 62858-07 for
	<pgsql-advocacy-postgresql.org@postgresql.org>;
	Tue, 13 Nov 2007 11:56:02 -0400 (AST)
Received: from mail43.e.nsc.no (mail43.e.nsc.no [193.213.115.43])
	by postgresql.org (Postfix) with ESMTP id B9E7B2E156A
	for <pgsql-advocacy@postgresql.org>;
	Tue, 13 Nov 2007 11:56:02 -0400 (AST)
Received: from [192.168.0.57] (062016190089.customer.alfanett.no
	[62.16.190.89]) (authenticated bits=0)
	by mail43.nsc.no (8.13.8/8.13.5) with ESMTP id lADFtx1W026455
	for <pgsql-advocacy@postgresql.org>;
	Tue, 13 Nov 2007 16:55:59 +0100 (MET)
From: "Leif B. Kristensen" <leif@solumslekt.org>
To: pgsql-advocacy@postgresql.org
Subject: Re: Avoiding upgrade backlash
User-Agent: KMail/1.9.7
References: <200711121442.31233.josh@agliodbs.com>
In-Reply-To: <200711121442.31233.josh@agliodbs.com>
X-Face: %iea8o"[SI'kMDS.`hz7lU=?\^lC9J-]CVjo;
	f{4-C:$?uVUEjyN~uYFn%*aH_c3d09U>=?iso-8859-1?q?x=0A=09TXtaoj=7EMV=2E8PgG7hik9=3BcCT2N6+u?=@Y{wH\p3*_f~FH9k,Wi74e[_l%.7b^'zJ)8S'^G<(=?iso-8859-1?q?=3D=0A=09zw8=5CPMC3=27=7BKl9=2EzL*ks!b6wA?=,c~'F`k&Vq|ELDGa|4<sl_DHXENz#~X_1qmPq+W;
	1LY2D9
MIME-Version: 1.0
Content-Disposition: inline
Date: Tue, 13 Nov 2007 16:55:59 +0100
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <200711131655.59501.leif@solumslekt.org>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200711/66
X-Sequence-Number: 12883

On Monday 12. November 2007, Josh Berkus wrote:
>I'm thinking that we need to warn everyone about:
>1) They need to use 8.3's pg_dump, not the old version, to upgrade

Isn't there a chicken-and-egg problem here? On my Gentoo system, I have 
always been forced to uninstall the old version before upgrading to a 
new version. In practice, that means that I have to do a full dump of 
the databases with the current pg_dump, delete or rename the data 
directory, and then restore after the upgrade.

I'd like to see a detailed howto on this ...
-- 
Leif Biberg Kristensen | Registered Linux User #338009
http://solumslekt.org/ | Cruising with Gentoo/KDE
My Jazz Jukebox: http://www.last.fm/user/leifbk/