From: Tom Lane <tgl@sss.pgh.pa.us>
To: Matthew T. O'Connor <matthew@zeut.net>
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:29:01 -0500
Message-ID: <6991.1143862141@sss.pgh.pa.us> (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>
"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.
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...)
regards, tom lane
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, matthew@zeut.net, jnasby@pervasive.com, gourish@gmail.com
Subject: Re: auto vacuuming
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>
* 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