pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jim Nasby <jnasby@pervasive.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: 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: Mon, 3 Apr 2006 11:09:51 -0500
Message-ID: <06443D67-9F59-4C98-9A5A-46F80980C611@pervasive.com> (raw)
In-Reply-To: <6991.1143862141@sss.pgh.pa.us>
References: <674d1f8a0603290206u55f114e1y7bfc2f83696fbada@mail.gmail.com>
	<20060331174802.GS49405@pervasive.com>
	<20060331185037.GF14204@surnet.cl>
	<442DA0CA.1050901@zeut.net>
	<6991.1143862141@sss.pgh.pa.us>

On Mar 31, 2006, at 9:29 PM, Tom Lane wrote:

> "Matthew T. O'Connor" <matthew@zeut.net> writes:
>> 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';
>
> Not really gonna help unless you insert a row into pg_autovacuum for
> each table in the database.

True.

> As I just commented in another reply, I don't actually believe in the
> value of disabling autovac entirely --- it should at least be able to
> fire when you are risking XID wraparound.  What could make sense is to
> push the thresholds up to very large values, such that autovac won't
> fire until you've forgotten manual vacuums for a very long time.
> And that you can already do on a per-database basis, using ALTER
> DATABASE SET.  (Or at least, it *should* work to do that; if the  
> autovac
> process fails to absorb per-db values for its GUC variables, then we
> ought to fix it.  I'm too lazy to test it right now...)

The problem with that is unless I missed a change in 8.1, autovac  
knows absolutely nothing about when manual vacuums have been run. To  
do that I'm pretty sure we'd need a catalog table that captured the  
statistic counts on each table when vacuum ran (and ideally an XID  
and a timestamp, too). If we end up with some kind of dirty page  
bitmap that might remove the need for that.

Even if tweaking the thresholds did work you still can't do it at a  
per-database level. It doesn't seem unreasonable to support different  
autovac settings at the database level.
--
Jim C. Nasby, Database Architect                decibel@decibel.org
Give your computer some brain candy! www.distributed.net Team #1828

Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"




--
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: <06443D67-9F59-4C98-9A5A-46F80980C611@pervasive.com>
Permalink:  ../06443D67-9F59-4C98-9A5A-46F80980C611@pervasive.com/
Also on:    postgresql.org/message-id/06443D67-9F59-4C98-9A5A-46F80980C611@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, tgl@sss.pgh.pa.us, matthew@zeut.net, gourish@gmail.com
  Subject: Re: auto vacuuming
  In-Reply-To: <06443D67-9F59-4C98-9A5A-46F80980C611@pervasive.com>
  References: <674d1f8a0603290206u55f114e1y7bfc2f83696fbada@mail.gmail.com> <20060331174802.GS49405@pervasive.com> <20060331185037.GF14204@surnet.cl> <442DA0CA.1050901@zeut.net> <6991.1143862141@sss.pgh.pa.us> <06443D67-9F59-4C98-9A5A-46F80980C611@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