pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: D'Arcy J.M. Cain <darcy@druid.net>
To: Radhika S <radhika.sambamurti@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Difference between Vacuum and Vacuum full
Date: Tue, 2 Oct 2007 22:02:01 -0400
Message-ID: <20071002220201.2722a499.darcy@druid.net> (raw)
In-Reply-To: <fe27bfd40710021845r59796586t8f9e672d0f4142d3@mail.gmail.com>
References: <fe27bfd40710021845r59796586t8f9e672d0f4142d3@mail.gmail.com>

On Tue, 2 Oct 2007 21:45:37 -0400
"Radhika S" <radhika.sambamurti@gmail.com> wrote:
> But this has bought me to the question of what exactly is the
> difference between vacuum and vacuum full. If both give back free
> space to the disk, then why have vacuum full.

Not quite.  "VACUUM FULL" returns space to the system.  "VACUUM" only
frees the space for use by the database.  In most cases a simple VACUUM
is all you need since you are going to just be asking for the space
back anyway eventually as your database grows.

-- 
D'Arcy J.M. Cain <darcy@druid.net>         |  Democracy is three wolves
http://www.druid.net/darcy/                |  and a sheep voting on
+1 416 425 1212     (DoD#0082)    (eNTP)   |  what's for dinner.



view thread (5+ messages)  latest in thread

Message-ID: <20071002220201.2722a499.darcy@druid.net>
Permalink:  ../20071002220201.2722a499.darcy@druid.net/
Also on:    postgresql.org/message-id/20071002220201.2722a499.darcy@druid.net

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: darcy@druid.net, radhika.sambamurti@gmail.com
  Subject: Re: Difference between Vacuum and Vacuum full
  In-Reply-To: <20071002220201.2722a499.darcy@druid.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox