Re: BUG #8058: CLUSTER and VACUUM FULL fail to free space

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: daniel(at)heroku(dot)com
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #8058: CLUSTER and VACUUM FULL fail to free space
Date: 2013-04-12 14:41:41
Message-ID: 17000.1365777701@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

daniel(at)heroku(dot)com writes:
> We have a somewhat high-churn table acting as a queue, and over time it's
> grown to be something like a gigabyte. I surmised it might be vanilla
> bloat, but the truth seems somewhat more exotic because both VACUUM FULL and
> CLUSTER generated absolutely no new free space.

> In the end, ALTER TABLE and CREATE TABLE ... (LIKE) ran nearly instantly and
> got the table size down to a few hundred K from 900M.

My money is on there being old idle transactions somewhere that kept
recently-dead rows from being reclaimable. If memory serves, VACUUM
FULL and CLUSTER will faithfully retain such rows, but of course a
manual data transfer like that wouldn't.

> We have retained the old bloated table so we can poke at it.

I think contrib/pgstattuple could tell you about dead tuples.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2013-04-12 14:47:52 Re: BUG #8059: sequence crash recovery is not working properly
Previous Message Andres Freund 2013-04-12 14:07:27 Re: BUG #8058: CLUSTER and VACUUM FULL fail to free space