Re: Running vacuum after delete does not remove all space allocated - Mailing list pgsql-general

From Scott Marlowe
Subject Re: Running vacuum after delete does not remove all space allocated
Date
Msg-id g2idcc563d11003311246wd6647af1v16ffc081c6261be5@mail.gmail.com
Whole thread Raw
In response to Running vacuum after delete does not remove all space allocated  (Chris Barnes <compuguruchrisbarnes@hotmail.com>)
List pgsql-general
On Wed, Mar 31, 2010 at 12:44 PM, Chris Barnes
<compuguruchrisbarnes@hotmail.com> wrote:
> I have deleted the rows in a table and vacuumed full, there appears to be
> space allocated that after a truncate it removes.
>
> Why is this?

It's how PostgreSQL is designed.  It recycles the space at a later
time, after vacuum has reclaimed the empty space and it puts new data
from inserts and updates into the now free space.  More efficient then
allocating and de-allocating all the time, and lowers fragmentation.

pgsql-general by date:

Previous
From: Bill Moran
Date:
Subject: Re: Select in temporary table
Next
From: Sylvain Lara
Date:
Subject: Re : Select in temporary table