Re: Database corruption help

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: John Lister <john(dot)lister-ps(at)kickstone(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Database corruption help
Date: 2009-02-15 10:18:10
Message-ID: 1234693090.4500.1142.camel@ebony.2ndQuadrant
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-hackers


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

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Kevin Grittner 2009-02-15 18:50:01 Re: Vacuum wait time problem
Previous Message Heikki Linnakangas 2009-02-14 08:26:11 Re: Database corruption help

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2009-02-15 14:08:51 Re: [COMMITTERS] pgsql: Explicitly bind gettext to the correct encoding on Windows.
Previous Message Jaime Casanova 2009-02-15 00:16:16 Re: Updates of SE-PostgreSQL 8.4devel patches (r1530)