From: | David G Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: VACUUM FULL doesn't reduce table size |
Date: | 2015-03-07 05:02:34 |
Message-ID: | 1425704554557-5840897.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 <
> pinker@
> > 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.
Really? This is vacuum full we are talking about. How would such a thing
occur?
The OP hasn't stated his version and I wouldn't assume 9.x
I have no experience here but given recent versions rewrite the table the
vacuum verbose output shown seems unusual.
David J.
--
View this message in context: http://postgresql.nabble.com/VACUUM-FULL-doesn-t-reduce-table-size-tp5840782p5840897.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2015-03-07 05:16:22 | Re: VACUUM FULL doesn't reduce table size |
Previous Message | Adrian Klaver | 2015-03-07 02:59:24 | Re: How to get plpython2 in /lib? |