pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Joel Stevenson <joelstevenson@mac.com>
To: pgsql-admin@postgresql.org
Subject: vacuumdb exclude tables option?
Date: Wed, 9 Aug 2006 11:24:03 -0700
Message-ID: <p06230915c0ffd2f2d63b@[192.168.0.9]> (raw)

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.

TIA,
Joel



view thread (8+ messages)  latest in thread

Message-ID: <p06230915c0ffd2f2d63b@[192.168.0.9]>
Permalink:  ../p06230915c0ffd2f2d63b@%5B192.168.0.9%5D/
Also on:    postgresql.org/message-id/p06230915c0ffd2f2d63b@[192.168.0.9]

 · 

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

* 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