pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jim C. Nasby <jnasby@pervasive.com>
To: Matthew T. O'Connor <matthew@zeut.net>
Cc: Gourish Singbal <gourish@gmail.com>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: auto vacuuming
Date: Fri, 31 Mar 2006 16:47:33 -0600
Message-ID: <20060331224733.GX49405@pervasive.com> (raw)
In-Reply-To: <442DA0CA.1050901@zeut.net>
References: <674d1f8a0603290206u55f114e1y7bfc2f83696fbada@mail.gmail.com>
	<20060331174802.GS49405@pervasive.com>
	<20060331185037.GF14204@surnet.cl>
	<442DA0CA.1050901@zeut.net>

On Fri, Mar 31, 2006 at 04:36:10PM -0500, Matthew T. O'Connor wrote:
> Alvaro Herrera wrote:
> >Jim C. Nasby wrote:
> >>On Wed, Mar 29, 2006 at 03:36:36PM +0530, Gourish Singbal wrote:
> >>>we are using postgresql 8.1.3 and wanted to enable autovacuuming for only
> >>>one of the many databases on the same postgresql cluster.
> >>>pg_autovacuum seems to allow to ignore only a particular table and not 
> >>>the
> >>>database since column vacrelid is OID from pg_class table  Are there any
> >>>suggestions to accomplish this tasks?.
> >>Currently there is no way to exclude entire databases from autovacuum.
> >
> >IIRC in one of the original patches I had added a way to do it.  It was
> >rejected however; it was argued that there was another mechanism to
> >disable it.  I don't remember what it was though.  The only possibility
> >that comes to mind is "ALTER DATABASE SET autovacuum TO off" but I don't
> >see why would it work.
> 
> 
> I think the closest approximation of disabling autovacuum on a per 
> database basis is to connect to the database in question and perform:
> 
> update pg_autovacuum set enabled = 'false';
> 
> This will prevent autovacuum from vacuuming or analyzing any of the 
> tables in the database, but will still check for XID wraparound.

Problem with that is any time you add a table you'd need to re-run that
command. Wouldn't be so bad if we had DDL triggers, but...
-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461



view thread (16+ messages)  latest in thread

Message-ID: <20060331224733.GX49405@pervasive.com>
Permalink:  ../20060331224733.GX49405@pervasive.com/
Also on:    postgresql.org/message-id/20060331224733.GX49405@pervasive.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: jnasby@pervasive.com, matthew@zeut.net, gourish@gmail.com
  Subject: Re: auto vacuuming
  In-Reply-To: <20060331224733.GX49405@pervasive.com>
  References: <674d1f8a0603290206u55f114e1y7bfc2f83696fbada@mail.gmail.com> <20060331174802.GS49405@pervasive.com> <20060331185037.GF14204@surnet.cl> <442DA0CA.1050901@zeut.net> <20060331224733.GX49405@pervasive.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