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

From Matthew T. O'Connor
Subject Re: Another small bug (pg_autovacuum)
Date
Msg-id 1063310892.13940.7.camel@zeutrh9
Whole thread Raw
In response to Re: Another small bug (pg_autovacuum)  (Christopher Browne <cbbrowne@acm.org>)
Responses Re: Another small bug (pg_autovacuum)  (Bruce Momjian <pgman@candle.pha.pa.us>)
Re: Another small bug (pg_autovacuum)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Thu, 2003-09-11 at 08:12, Christopher Browne wrote:
> Something I am feeling a little suspicious of is that I haven't seen,
> in the logs, pg_autovacuum looking at pg_ tables.  
> 
> I know that if we don't periodically vacuum such system tables as
> pg_class, pg_attribute, pg_statistic, and pg_type, they can get to
> "pretty evil size."
> 
> [Rummaging around...]  These tables are being added for template1, but
> apparently not for "main" databases.  That looks like a bit of a fly
> in the ointment...

I designed it that way.  It was my understanding that all of the system
tables pg_class etc... are shared tables, available in all databases,
but actually stored as only one central set of real tables.  Hence
vacuuming pg_class from template1 helps every database that accesses
pg_class.

Did I make a design error?




pgsql-hackers by date:

Previous
From: "Matthew T. O'Connor"
Date:
Subject: Re: Another small bug (pg_autovacuum)
Next
From: Tom Lane
Date:
Subject: Re: massive quotes?