Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 5A0509FBBA9 for ; Thu, 10 May 2007 22:05:31 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 08341-08 for ; Thu, 10 May 2007 22:05:22 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id B482E9FB4F1 for ; Thu, 10 May 2007 22:05:27 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.3 Received: from server.firetrust.net (mailserver.firetrust.com [209.213.221.13]) by svr4.postgresql.org (Postfix) with ESMTP id A12745AF025 for ; Fri, 11 May 2007 01:05:26 +0000 (GMT) Received: from localhost.localdomain (203-97-61-135.dsl.clear.net.nz [203.97.61.135]) by server.firetrust.net (8.14.1/8.14.1) with SMTP id l4B15Dd0009730 for ; Fri, 11 May 2007 13:05:14 +1200 Date: Fri, 11 May 2007 13:05:03 +1200 From: Steve Holdoway To: pgsql-admin@postgresql.org Subject: Re: upgrade 8.0.3 -> 8.2.4 Message-Id: <20070511130503.6630c74e.steve.holdoway@firetrust.com> In-Reply-To: <464332D5.1000208@drivefaster.net> References: <20070510170751.348e09a6.steve.holdoway@firetrust.com> <464332D5.1000208@drivefaster.net> Organization: Firetrust Ltd X-Mailer: Sylpheed version 2.3.0beta5 (GTK+ 2.8.20; i486-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.90.2/3225/Thu May 10 20:08:21 2007 on server.firetrust.net X-Virus-Status: Clean X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.136 tagged_above=0 required=5 tests=BAYES_50=0.001, FORGED_RCVD_HELO=0.135 X-Spam-Level: X-Archive-Number: 200705/90 X-Sequence-Number: 25410 Thanks, I knew about that one, and spent half a day cleaning up the data set before transfer. That was exciting... Cheers, Steve On Thu, 10 May 2007 08:57:25 -0600 Dan Harris wrote: > Steve Holdoway wrote: > > Are there any gotchas? I've got the opportunity to move to another database server for this application and yould like to take the opportunity to upgrade at the same time. > > Yes. One of them that got me was that in 8.0.x, you could insert "invalid" > unicode byte sequences and it would warn you but accept them just fine. In 8.2, > this is strictly enforced and you will not be able to restore your dump file > without running a utility to "fix" the dump file. > > This change has prevented me from doing the upgrade as my dump file is nearly > 100GB and the programming design of this utility requires that the whole file be > read into RAM before it begins processing it ( I've let it run for days and it > doesn't complete ). I didn't think I had any Unicode in my database at all, but > I guess there are a few instances of "noise" in there that cause this.. > > Hopefully this doesn't block someone else from upgrading. > > -Dan > > ---------------------------(end of broadcast)--------------------------- > TIP 4: Have you searched our list archives? > > http://archives.postgresql.org