pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: adey <adey11@gmail.com>
To: Scott Marlowe <smarlowe@g2switchworks.com>
Cc: Joel Stevenson <joelstevenson@mac.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: vacuumdb exclude tables option?
Date: Thu, 10 Aug 2006 16:01:47 +1200
Message-ID: <1c66bda80608092101m272dc6d3pd0145d4fd640cc3@mail.gmail.com> (raw)
In-Reply-To: <1155148097.20252.106.camel@state.g2switchworks.com>
References: <p06230915c0ffd2f2d63b@192.168.0.9>
	<1155148097.20252.106.camel@state.g2switchworks.com>

Does autovacuum replace the need for a FULL vacuum please (to recover free
space, etc)?

On 8/10/06, Scott Marlowe <smarlowe@g2switchworks.com> wrote:
>
> On Wed, 2006-08-09 at 13:24, Joel Stevenson wrote:
> > Hi,
> >
> > I have a database that includes both highly transactional tables and
> > archive tables - OLTP and OLAP mixed together.  Some of the archival
> > tables, which only experience inserts and reads, not updates or
> > deletes, contain many millions of rows and so they take a *long* time
> > to vacuum.  Is there currently any means to exclude only these tables
> > from vacuumdb operations other than explicitly vacuuming all the
> > other tables and explicity skipping the archival tables?
> >
> > If not, are there any plans to add a command line switch to vacuumdb
> > to exclude tables from it's operation, ala 'vacuumdb -d mytest -x
> > archive_tab1 -x archive_tab2 -x archive_tab3'?  I searched the list
> > archives but didn't see anything about being able to do this.
> > Something like this would save many hours of useless vacuuming in
> > this particular setup.
>
> Does autovacuum fail you in this quest?  I've found it's pretty good
> about leaving along tables that don't need vacuuming.  It's usually the
> other way around that people have problems with, autovacuum NOT
> vacuuming tables that need vacuuming often enough.
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
>

view thread (8+ messages)  latest in thread

Message-ID: <1c66bda80608092101m272dc6d3pd0145d4fd640cc3@mail.gmail.com>
Permalink:  ../1c66bda80608092101m272dc6d3pd0145d4fd640cc3@mail.gmail.com/
Also on:    postgresql.org/message-id/1c66bda80608092101m272dc6d3pd0145d4fd640cc3@mail.gmail.com

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: adey11@gmail.com, smarlowe@g2switchworks.com, joelstevenson@mac.com
  Subject: Re: vacuumdb exclude tables option?
  In-Reply-To: <1c66bda80608092101m272dc6d3pd0145d4fd640cc3@mail.gmail.com>
  References: <p06230915c0ffd2f2d63b@192.168.0.9> <1155148097.20252.106.camel@state.g2switchworks.com> <1c66bda80608092101m272dc6d3pd0145d4fd640cc3@mail.gmail.com>

* 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