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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
