pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@commandprompt.com>
Cc: Jim C. Nasby <jnasby@pervasive.com>
Cc: Gourish Singbal <gourish@gmail.com>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: auto vacuuming
Date: Fri, 31 Mar 2006 22:17:47 -0500
Message-ID: <6933.1143861467@sss.pgh.pa.us> (raw)
In-Reply-To: <20060331185037.GF14204@surnet.cl>
References: <674d1f8a0603290206u55f114e1y7bfc2f83696fbada@mail.gmail.com>
	<20060331174802.GS49405@pervasive.com>
	<20060331185037.GF14204@surnet.cl>

Alvaro Herrera <alvherre@commandprompt.com> writes:
> Jim C. Nasby wrote:
>> 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.

I can't think of one either.  Real question is, why would you want to?
Disabled autovac would for instance be unable to protect you against XID
wraparound, which IMHO is one of the major advantages of running it at
all.

The handwriting on the wall says that autovac will soon be on by
default, and perhaps become not-disablable some day after that
(like the second or third time we hear from someone who's lost
their data to XID wraparound after disabling it).

So if there's a really convincing use-case for locking autovac out
of specific databases, we'd better hear it soon.

			regards, tom lane



view thread (16+ messages)  latest in thread

Message-ID: <6933.1143861467@sss.pgh.pa.us>
Permalink:  ../6933.1143861467@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/6933.1143861467@sss.pgh.pa.us

 · 

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: tgl@sss.pgh.pa.us, alvherre@commandprompt.com, jnasby@pervasive.com, gourish@gmail.com
  Subject: Re: auto vacuuming
  In-Reply-To: <6933.1143861467@sss.pgh.pa.us>
  References: <674d1f8a0603290206u55f114e1y7bfc2f83696fbada@mail.gmail.com> <20060331174802.GS49405@pervasive.com> <20060331185037.GF14204@surnet.cl> <6933.1143861467@sss.pgh.pa.us>

* 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