Re: Another small bug (pg_autovacuum) - Mailing list pgsql-hackers

From Christopher Browne
Subject Re: Another small bug (pg_autovacuum)
Date
Msg-id 60k78dstn9.fsf@dev6.int.libertyrms.info
Whole thread Raw
In response to Re: Another small bug (pg_autovacuum)  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
matthew@zeut.net ("Matthew T. O'Connor") writes:
> So we would have a problem if commands that effect these tables are done
> from lots of different databases.  In reality, I don't think these
> tables change that much (pg_database, pg_shadow, and pg_group), and most
> of commands that do effect these tables are usually done from template1.

I wouldn't necessarily assume the latter ("usually done from
template1"), but these surely seem to be candidates for being fairly
infrequent.  

And if they _were_ being touched frequently, would they not trigger
vacuums in the databse that they were being touched in?

In any case, if there are three tables that pg_autovacuum never
touches that _normally_ are pretty quiet, this does not appear to be a
grand disaster.
-- 
output = ("cbbrowne" "@" "libertyrms.info")
<http://dev6.int.libertyrms.com/>
Christopher Browne
(416) 646 3304 x124 (land)


pgsql-hackers by date:

Previous
From: Tilo Schwarz
Date:
Subject: Re: plpython
Next
From: Manfred Spraul
Date:
Subject: Re: [PATCHES] Reorganization of spinlock defines