pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruno Wolff III <bruno@wolff.to>
To: Joel Stevenson <joelstevenson@mac.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: vacuumdb exclude tables option?
Date: Fri, 18 Aug 2006 10:25:48 -0500
Message-ID: <20060818152548.GA24101@wolff.to> (raw)
In-Reply-To: <p06230915c0ffd2f2d63b@[192.168.0.9]>
References: <p06230915c0ffd2f2d63b@[192.168.0.9]>

On Wed, Aug 09, 2006 at 11:24:03 -0700,
  Joel Stevenson <joelstevenson@mac.com> wrote:
> 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?

Take a look at:
http://developer.postgresql.org/docs/postgres/routine-vacuuming.html#AUTOVACUUM
There will be a way to have per table settings in 8.2, though the interface
for setting things up is klunky.
I also seem to remember some discussion about having a separate transaction
for each table being cleaned as a new feature. This helps with some other
problems. There will still be an issue if you mix some long running queries
with frequent updates in the same database, as the long running queries can
prevent recovering a lot of rows in frequently updated tables. I have seen
discussions of people brainstorming about this problem, but I don't remember
anyone coming up with a great solution.



view thread (8+ messages)  latest in thread

Message-ID: <20060818152548.GA24101@wolff.to>
Permalink:  ../20060818152548.GA24101@wolff.to/
Also on:    postgresql.org/message-id/20060818152548.GA24101@wolff.to

 · 

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: bruno@wolff.to, joelstevenson@mac.com
  Subject: Re: vacuumdb exclude tables option?
  In-Reply-To: <20060818152548.GA24101@wolff.to>
  References: <p06230915c0ffd2f2d63b@[192.168.0.9]> <20060818152548.GA24101@wolff.to>

* 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