pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Chris Hoover <revoohc@gmail.com>
Cc: Anthony Ransley <anthonyr@aurema.com>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: Autovacuum ideas
Date: Wed, 12 Apr 2006 11:15:53 -0400
Message-ID: <20060412151553.GD23855@surnet.cl> (raw)
In-Reply-To: <1d219a6f0604120753h1cabb4c2n60f53403225dcf81@mail.gmail.com>
References: <1d219a6f0604111602m62445e60h425c5dd59219606e@mail.gmail.com>
	<443C39ED.6050706@aurema.com>
	<1d219a6f0604120753h1cabb4c2n60f53403225dcf81@mail.gmail.com>

Chris Hoover wrote:
> This is what we are doing today (except we are on Linux :) ).  However,
> since there is talk of making autovacuum on by default and the advantages of
> having it run, it would be nice to be able to block out hours that it can
> not run.  It would also be very nice to have the database take care of all
> of this via the config file and/or tables.  That way, no external programs
> (cron or what ever) would be needed.
> 
> Even nicer would be to have the time exclusion granular enough to be table
> to exclude only certain tables.  That way autovacuum can do it's work as
> needed on the majority of the tables, but tables that the DBA knows will
> cause problems during business hours could be excluded until the slow time.
> 
> Any comments on this?

I don't think autovacuum will be on by default until we have a way to
configure rush hours, maintenance windows, etc.

The system I envision has tables grouped in some way, and maintenance
windows would operate on table groups.  For example you will be able to
include the fat table in a (possibly otherwise empty) group, and have
that group not be processed during "work hours"; the rest of the tables
would continue to be vacuumed at all times.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support



view thread (14+ messages)  latest in thread

Message-ID: <20060412151553.GD23855@surnet.cl>
Permalink:  ../20060412151553.GD23855@surnet.cl/
Also on:    postgresql.org/message-id/20060412151553.GD23855@surnet.cl

 · 

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: alvherre@commandprompt.com, revoohc@gmail.com, anthonyr@aurema.com
  Subject: Re: Autovacuum ideas
  In-Reply-To: <20060412151553.GD23855@surnet.cl>
  References: <1d219a6f0604111602m62445e60h425c5dd59219606e@mail.gmail.com> <443C39ED.6050706@aurema.com> <1d219a6f0604120753h1cabb4c2n60f53403225dcf81@mail.gmail.com> <20060412151553.GD23855@surnet.cl>

* 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