Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id C284D633163 for ; Sun, 15 Feb 2009 06:35:34 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 33579-01 for ; Sun, 15 Feb 2009 06:35:28 -0400 (AST) Received: from mx1.hub.org (mx1.hub.org [200.46.208.106]) by mail.postgresql.org (Postfix) with ESMTP id 2BBA7633148 for ; Sun, 15 Feb 2009 06:17:50 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from outmail128148.authsmtp.net (outmail128148.authsmtp.net [62.13.128.148]) by mx1.hub.org (Postfix) with ESMTP id 9336D1259CD2 for ; Sun, 15 Feb 2009 06:17:48 -0400 (AST) Received: from mail-c193.authsmtp.com (mail-c193.authsmtp.com [62.13.128.118]) by punt5.authsmtp.com (8.14.2/8.14.2/Kp) with ESMTP id n1FAF5xL004058; Sun, 15 Feb 2009 10:15:05 GMT Received: from [192.168.0.3] (85-211-101-162.dyn.gotadsl.co.uk [85.211.101.162]) (authenticated bits=0) by mail.authsmtp.com (8.14.2/8.14.2/Kp) with ESMTP id n1FAF4mS051098; Sun, 15 Feb 2009 10:15:04 GMT Subject: Re: Database corruption help From: Simon Riggs To: Tom Lane Cc: John Lister , pgsql-hackers@postgresql.org In-Reply-To: <3161.1234541940@sss.pgh.pa.us> References: <507152DDF8AB4DF093BD01A8BEC7C659@squarepi.com> <17205.1234200693@sss.pgh.pa.us> <4990840C.4090900@kickstone.com> <20151.1234208044@sss.pgh.pa.us> <49908D72.7040904@kickstone.com> <25753.1234224090@sss.pgh.pa.us> <4991338B.704@kickstone.com> <4994906B.6090408@kickstone.com> <17204.1234474784@sss.pgh.pa.us> <4994987F.1030204@kickstone.com> <17764.1234476783@sss.pgh.pa.us> <4994A45B.4030707@kickstone.com> <49952D33.3000707@kickstone.com> <3161.1234541940@sss.pgh.pa.us> Content-Type: text/plain Date: Sun, 15 Feb 2009 10:18:10 +0000 Message-Id: <1234693090.4500.1142.camel@ebony.2ndQuadrant> Mime-Version: 1.0 X-Mailer: Evolution 2.12.0 Content-Transfer-Encoding: 7bit X-Server-Quench: 83ab4aed-fb49-11dd-8a51-002264978518 X-AuthRoute: OCdxZQATClZOTQEd DAteCiNZVAwpPBRK HVkIKg5MJUcNSQVJ NksadRtFaQBba1xT HGQLW11EUV17WGZ/ aw8fZQBDYEtPQQRq UVZIRFBNFgBqBAMB SEAfJGgEc1gleHtx ZU9qEHFdVEc0fUUs EEoFQDkbMzVkYX0e URQMagsFdQJXfh9H aFZ7XXQFZGQPKBg1 TUcAHxkaHhhlExEd bggRJFgbWktDFTkm XQ0aATQoGwUFSiEr RyAn X-Authentic-SMTP: 61633235383639.pelican.dmpriest.net.uk:1378/Kp X-Report-SPAM: If SPAM / abuse - report it at: http://www.authsmtp.com/abuse X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200902/813 X-Sequence-Number: 134103 On Fri, 2009-02-13 at 11:19 -0500, Tom Lane wrote: > Aside from the "how did this happen" puzzle, the real point of any > investigation of course ought to be whether we can make heap_page_prune > more robust. At the very least it's undesirable to be leaving the page > in a state where VACUUM FULL will decide it can't shrink. I think it would be useful to have a function that can scan a table to see if this issue exists. ISTM if it has happened once it can have happened many times. It would be useful to have some more trouble reports so we can assess the size and scope of this problem. -- Simon Riggs www.2ndQuadrant.com PostgreSQL Training, Services and Support