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 B3D04D8736 for ; Thu, 8 Sep 2005 12:29:53 -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 27242-06 for ; Thu, 8 Sep 2005 15:29:52 +0000 (GMT) Received: from mailhub2.sghms.ac.uk (mailhub2.sghms.ac.uk [194.82.51.8]) by svr1.postgresql.org (Postfix) with ESMTP id 0E678D8733 for ; Thu, 8 Sep 2005 12:29:51 -0300 (ADT) Received: from [194.82.51.24] (helo=imail) by mailhub2.sghms.ac.uk with esmtp (Exim 4.24) id 1EDOLA-0006dr-Fn; Thu, 08 Sep 2005 16:29:28 +0100 Received: from [172.16.20.3] (mrc1-003.sghms.ac.uk [172.16.20.3]) by imail.sghms.ac.uk (iPlanet Messaging Server 5.2 HotFix 2.06 (built Mar 28 2005)) with ESMTPA id <0IMI006U98D48V@imail.sghms.ac.uk>; Thu, 08 Sep 2005 16:29:28 +0100 (BST) Date: Thu, 08 Sep 2005 16:26:16 +0100 From: Adam Witney Subject: Re: pg_dump error... Follow up In-reply-to: <6689.1126190796@sss.pgh.pa.us> To: Tom Lane Cc: Alvaro Herrera , pgsql-admin , Michael Fuhr Message-id: MIME-version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT User-Agent: Microsoft-Entourage/10.1.1.2418 X-MailScanner-Information: Please contact sysadmin at sghms.ac.uk for more information X-MailScanner-MH2: No Virues detected X-MailScanner-SpamCheck: not spam, SpamAssassin (score=-2.82, required 5, autolearn=not spam, ALL_TRUSTED -2.82) X-MailScanner-From: awitney@sgul.ac.uk X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.012 required=5 tests=[AWL=0.012] X-Spam-Level: X-Archive-Number: 200509/81 X-Sequence-Number: 18818 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... Or could it be from a different database altogether? (although none of the others get much updates at all) Thanks again adam -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.