Re: VACUUM FULL doesn't reduce table size

From: pinker <pinker(at)onet(dot)eu>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: VACUUM FULL doesn't reduce table size
Date: 2015-03-09 11:25:25
Message-ID: 1425900325506-5841086.post@n5.nabble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Vick Khera wrote
> On Fri, Mar 6, 2015 at 5:59 AM, pinker &lt;

> pinker@

> &gt; wrote:
>
>> I have deleted a large number of records from my_table, which originally
>> had
>> 288 MB. Then I ran vacuum full to make the table size smaller. After this
>> operation size of the table remains the same, despite of the fact that
>> table
>>
>
> If your remaining records were in say, block 2 and block 10000, then the
> blocks in between won't be returned to the system.
>
> You could achieve your "fix" by running cluster on the table, which will
> rewrite the table in-place. There are also scripts out there that do
> in-place compaction by running targeted updates and vacuum commands to get
> the empty pages at the end of the files truncated off the file.

I have tried many combinations of VACUUM, VACUUM FULL and CLUSTER after
first failed VACUUM FULL and nothing works...

--
View this message in context: http://postgresql.nabble.com/VACUUM-FULL-doesn-t-reduce-table-size-tp5840782p5841086.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message John McKown 2015-03-09 12:11:07 Re: Creating composite keys from csv
Previous Message pinker 2015-03-09 11:22:56 Re: VACUUM FULL doesn't reduce table size