X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 2F9C3D8871 for ; Thu, 8 Sep 2005 12:55:26 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 33624-08 for ; Thu, 8 Sep 2005 15:55:24 +0000 (GMT) Received: from mx1.surnet.cl (mx2.surnet.cl [216.155.73.181]) by svr1.postgresql.org (Postfix) with ESMTP id E084CD8809 for ; Thu, 8 Sep 2005 12:55:23 -0300 (ADT) Received: from unknown (HELO cluster.surnet.cl) ([216.155.73.165]) by mx1.surnet.cl with ESMTP; 08 Sep 2005 11:55:12 -0400 X-IronPort-AV: i="3.96,179,1122868800"; d="scan'208"; a="6698207:sNHT56981256" Received: from alvh.no-ip.org (216.155.85.134) by cluster.surnet.cl (7.0.043) (authenticated as alvherre@surnet.cl) id 4317C634000C3550; Thu, 8 Sep 2005 11:55:22 -0400 Received: by alvh.no-ip.org (Postfix, from userid 1000) id A7E5EC2DC74; Thu, 8 Sep 2005 11:56:21 -0400 (CLT) Date: Thu, 8 Sep 2005 11:56:21 -0400 From: Alvaro Herrera To: Adam Witney Cc: Tom Lane , pgsql-admin , Michael Fuhr Subject: Re: pg_dump error... Follow up Message-ID: <20050908155621.GB13949@surnet.cl> Mail-Followup-To: Adam Witney , Tom Lane , pgsql-admin , Michael Fuhr References: <6689.1126190796@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.10i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=2.343 required=5 tests=[AWL=-0.483, DNS_FROM_RFC_ABUSE=0.374, DNS_FROM_RFC_POST=1.376, FORGED_RCVD_HELO=0.05, RCVD_IN_NJABL_PROXY=1.026] X-Spam-Level: ** X-Archive-Number: 200509/82 X-Sequence-Number: 18819 On Thu, Sep 08, 2005 at 04:26:16PM +0100, Adam Witney wrote: > On 8/9/05 3:46 pm, "Tom Lane" wrote: > > > Adam Witney writes: > >> Here you go.... > > > >> pg_filedump-3.0/pg_filedump -i -f -R 34318 34320 134401986.1 > > > > Thanks. What it looks like to me is that block 34320 (really 165392) > > is data from some other file altogether. It's evidently still Postgres > > heap data, but instead of having 3 non-null columns as any toast row > > ought to have, these rows have 77 columns many of which are nulls. > > They've got OIDs, too. Possibly you can work out which table these > > rows really belong to. It looks like this ought to be block 415664 > > of whatever table it belongs to (which would make it block 22448 of > > the xxx.3 file of that table, if I did the math right). > > I only have one file with a .3 in that database... How many columns does that table have? > Or could it be from a different database altogether? (although none of > the others get much updates at all) It's not impossible ... To Tom: could this be caused by a WAL recovery that wrote a page image to the wrong table? I guess it is very unlikely because the CRC of the WAL record would likely not match, but it's an idea. -- Alvaro Herrera -- Valdivia, Chile Architect, www.EnterpriseDB.com "At least to kernel hackers, who really are human, despite occasional rumors to the contrary" (LWN.net)