pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Nick Urbanik <nicku@nicku.org>
To: pgsql-admin@postgresql.org
Subject: Re: How overcome wait for vacuum full?
Date: Wed, 16 May 2007 09:16:17 +1000
Message-ID: <20070515231616.GH5264@nicku.org> (raw)
In-Reply-To: <20070515225313.GV12731@alvh.no-ip.org>
References: <20070515221356.GG5264@nicku.org>
	<20070515225313.GV12731@alvh.no-ip.org>

Thank you Alvaro,

On 15/05/07 18:53 -0400, Alvaro Herrera wrote:
>Instead of waiting a month for the time when you can take the
>application offline (thus accumulating a month's worth of dead tuples),
>run a non-full vacuum more often (say, once a day or more).  It doesn't
>lock the table so the app can continue to be online while it runs.

Yes, it is vacuumed non-full regularly.  However, for some reason,
only a full vacuum will recover the space.

>If you have too many dead tuples and are desperate to get the table in a
>reasonable non-bloated state, try CLUSTER instead of VACUUM FULL.  It
>might finish faster.

1. If I am running vacuum full on the database as:

vacuum full verbose;

   without specifying a table, if I interrupt it, will the vacuuming of
   the other tables that have already been vacuumed be undone?  How
   far is vacuuming rolled back if I interrupt it in this case?

2. If I interrupt the vacuum, and run cluster,  how long do you think
   cluster might take relative to a full vaccuum?  Is it likely to
   save disk space? (since that is the aim rather than speeding things
   up)

   The value of reltuples and relpages for this table are: reltuples:
   572208, relpages 187502

3. This is PostgreSQL 7.3.8.
-- 
Nick Urbanik   RHCE         http://nicku.org        nicku@nicku.org
GPG: 7FFA CDC7 5A77 0558 DC7A 790A 16DF EC5B BB9D 2C24 ID: BB9D2C24

view thread (12+ messages)  latest in thread

Message-ID: <20070515231616.GH5264@nicku.org>
Permalink:  ../20070515231616.GH5264@nicku.org/
Also on:    postgresql.org/message-id/20070515231616.GH5264@nicku.org

 · 

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-admin@postgresql.org
  Cc: nicku@nicku.org
  Subject: Re: How overcome wait for vacuum full?
  In-Reply-To: <20070515231616.GH5264@nicku.org>

* 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