pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Darcy Buskermolen <darcy@wavefire.com>
To: pgsql-admin@postgresql.org
Cc: Chris Hoover <revoohc@gmail.com>
Cc: Anthony Ransley <anthonyr@aurema.com>
Subject: Re: Autovacuum ideas
Date: Wed, 12 Apr 2006 08:39:08 -0700
Message-ID: <200604120839.08978.darcy@wavefire.com> (raw)
In-Reply-To: <1d219a6f0604120753h1cabb4c2n60f53403225dcf81@mail.gmail.com>
References: <1d219a6f0604111602m62445e60h425c5dd59219606e@mail.gmail.com>
	<443C39ED.6050706@aurema.com>
	<1d219a6f0604120753h1cabb4c2n60f53403225dcf81@mail.gmail.com>

On Wednesday 12 April 2006 07:53, 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.

What about leaving autovac running, and poke values into the pg_autovacuum 
table via cron? 

>
>
> Any comments on this?
>
> Chris
>
> On 4/11/06, Anthony Ransley <anthonyr@aurema.com> wrote:
> > Hi Chris Hoover,
> >
> >
> > There is already a method for this! Can i suggest that you set a O/S
> > schedule to simple run vacuumdb.exe at the desired time, preferable late
> > evening, as the vacuum of large databases can take all night, based on
> > my DBA experience. Don't for get to setup the uses of password files, as
> > vacuumdb.exe will require a password and user account each end every
> > time it runs.
> >
> > Anthony.
> >
> > Chris Hoover wrote:
> > > I have an idea/request for the autovacuum daemon.
> > >
> > > As far as I can tell, there is no way to tell the daemon to only do
> > > it's work between certain hours. Could this be added as an option? In
> > > my situation, I have tables that if vacuumed during the day would
> > > cause a noticeable slowdown to my users and has therefore been deemed
> > > unacceptable by management. This is one thing that is preventing me
> > > from turning on autovacuun,. However, due to the activity on them,
> > > they really need to be vacuumed daily. It would be nice to be able to
> > > tell autovacuum to run, but have a way to tell it to always sleep
> > > during these hours ( i.e. 7am to 5pm daily). Has there been any
> > > thought into a feature like this?
> > >
> > > Thanks,
> > >
> > > Chris

-- 
Darcy Buskermolen
Wavefire Technologies Corp.

http://www.wavefire.com
ph: 250.717.0200
fx: 250.763.1759



view thread (14+ messages)  latest in thread

Message-ID: <200604120839.08978.darcy@wavefire.com>
Permalink:  ../200604120839.08978.darcy@wavefire.com/
Also on:    postgresql.org/message-id/200604120839.08978.darcy@wavefire.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: darcy@wavefire.com, revoohc@gmail.com, anthonyr@aurema.com
  Subject: Re: Autovacuum ideas
  In-Reply-To: <200604120839.08978.darcy@wavefire.com>
  References: <1d219a6f0604111602m62445e60h425c5dd59219606e@mail.gmail.com> <443C39ED.6050706@aurema.com> <1d219a6f0604120753h1cabb4c2n60f53403225dcf81@mail.gmail.com> <200604120839.08978.darcy@wavefire.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