Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 7F3FC14BD8A1 for ; Wed, 9 Nov 2011 11:58:00 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 33861-01-7 for ; Wed, 9 Nov 2011 15:57:54 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.8.0-rc2 Received: from gw.wicourts.gov (gwmta.wicourts.gov [165.219.244.99]) by mail.postgresql.org (Postfix) with ESMTP id 012B71286994 for ; Wed, 9 Nov 2011 11:57:39 -0400 (AST) Received: from Courts-MTA by gw.wicourts.gov with Novell_GroupWise; Wed, 09 Nov 2011 09:57:40 -0600 Message-Id: <4EBA4E910200002500042BEC@gw.wicourts.gov> X-Mailer: Novell GroupWise Internet Agent 8.0.1 Date: Wed, 09 Nov 2011 09:57:37 -0600 From: "Kevin Grittner" To: "Ruslan A. Bondar" Cc: Subject: Re: How to deal with corrupted database? References: <20111109150225.076c2f38@list.ru> <4EBA460E0200002500042BCD@gw.wicourts.gov> <20111109195350.51c1b014@list.ru> In-Reply-To: <20111109195350.51c1b014@list.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-3.101 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RP_MATCHES_RCVD=-1.201 X-Spam-Level: X-Archive-Number: 201111/32 X-Sequence-Number: 38626 "Ruslan A. Bondar" wrote: > No, this was a clean install of 9.0.x. Then it isn't related to the issue I raised. > Maybe It was upgraded from 9.0.3 to 9.0.4. I'm not sure. You don't normally use pg_upgrade for that; this was a pg_upgrade bug. -Kevin