| From: | Jim Nasby <jnasby(at)pervasive(dot)com> |
|---|---|
| To: | Matthew T(dot) O'Connor <matthew(at)zeut(dot)net> |
| Cc: | Gourish Singbal <gourish(at)gmail(dot)com>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: auto vacuuming |
| Date: | 2006-04-03 16:09:31 |
| Message-ID: | 0EC17362-8EA3-468C-BC3A-19A0EB9A3A64@pervasive.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Mar 31, 2006, at 5:45 PM, Matthew T. O'Connor wrote:
>>> 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...
>>
>
> Probably a dumb comment, but can you set a default value for the
> enabled column?
As Tom pointed out, that wouldn't help because rows aren't
automatically added to pg_autovacuum.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2006-04-03 16:09:51 | Re: auto vacuuming |
| Previous Message | Grega Bremec | 2006-04-03 06:10:33 | Re: FW: Setting up of PITR system. |