pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Decibel! <decibel@decibel.org>
To: Nick Fankhauser <nickf@doxpop.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Specific questions about wraparound and vacuum
Date: Wed, 8 Aug 2007 15:46:49 -0500
Message-ID: <20070808204649.GQ20424@nasby.net> (raw)
In-Reply-To: <bb2fe60f0708080907x1d8aa6dct5aa3cb1e1ba15897@mail.gmail.com>
References: <bb2fe60f0708080907x1d8aa6dct5aa3cb1e1ba15897@mail.gmail.com>

On Wed, Aug 08, 2007 at 12:07:14PM -0400, Nick Fankhauser wrote:
> 2) If a regular (non-full) vacuum will not reset the XID. Will a
> dump/restore take care of wraparound? We have done this in the past for
> space reclamation because we seem to be able to dump/restore more quickly
> than we can do a full vacuum.

If you're doing that you need to re-evaluate your vacuuming strategy and
possibly your free space map settings. You should normally never need to
use pg_dump(all) or vacuum full to reclaim space.

If you've got the ability to take enough downtime to dump and restore,
you should really use that opportunity to upgrade to a modern version,
too.
-- 
Decibel!, aka Jim Nasby                        decibel@decibel.org
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)

view thread (11+ messages)  latest in thread

Message-ID: <20070808204649.GQ20424@nasby.net>
Permalink:  ../20070808204649.GQ20424@nasby.net/
Also on:    postgresql.org/message-id/20070808204649.GQ20424@nasby.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-admin@postgresql.org
  Cc: decibel@decibel.org, nickf@doxpop.com
  Subject: Re: Specific questions about wraparound and vacuum
  In-Reply-To: <20070808204649.GQ20424@nasby.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