Re: Table Bloat still there after the Vacuum

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: akp geek <akpgeek(at)gmail(dot)com>
Cc: Bill Moran <wmoran(at)potentialtech(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Table Bloat still there after the Vacuum
Date: 2010-04-26 15:43:28
Message-ID: 19086.1272296608@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

akp geek <akpgeek(at)gmail(dot)com> writes:
> * "Orders": found 0 removable, 27164544 nonremovable row versions in 518971
> pages*
> *DETAIL: 27126176 dead row versions cannot be removed yet.*

So there isn't anything vacuum can do right now. You've apparently got
an old open transaction, which is blocking vacuum from removing those
dead rows because the open transaction should still be able to see them
if it were to look. You need to close that transaction, and then do a
vacuum full (and probably a reindex after that).

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Scott Marlowe 2010-04-26 15:51:07 Re: Start-up script for few clusters: just add water?
Previous Message Vincenzo Romano 2010-04-26 15:41:20 Re: Inheritance efficiency