pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Steve Crawford <scrawford@pinpointresearch.com>
To: pgsql-admin@postgresql.org
Subject: Re: Excessive growth of pg_attribute and other system tables
Date: Thu, 17 Mar 2005 16:37:16 -0800
Message-ID: <200503171637.16975.scrawford@pinpointresearch.com> (raw)
In-Reply-To: <28709.1111103484@sss.pgh.pa.us>
References: <200503171515.38214.scrawford@pinpointresearch.com>
	<28709.1111103484@sss.pgh.pa.us>

On Thursday 17 March 2005 3:51 pm, Tom Lane wrote:
> Steve Crawford <scrawford@pinpointresearch.com> writes:
> > My autovacuum config is running and I do see regular periodic
> > vacuums of these pg_ tables but still they grow.
>
> Do you have the FSM settings set large enough to account for all
> the free space?

max_fsm_pages = 20000
max_fsm_relations = 1000

I just poked through the cluster. I have 6 user databases plus 
template0 and template1. Total tables in the cluster has reached 
slightly over 1,000 user tables plus all the system tables in the 8 
databases. Does this indicate that I need to increase 
max_fsm_relations to greater than the total number of tables in the 
cluster? If so it's not a problem as bumping it to 2000 will only 
cost me ~50k of my 4G memory plus a bit more since max_fsm_pages 
would have to be increased to at least 32000.

> Also you might want to check for newer versions of autovacuum.  I
> recall that the earlier releases had bugs that sometimes made it
> skip vacuuming tables that should be vacuumed.

pg_autovacuum is from 7.4.6 release and is showing periodic vacuums of 
the problem tables. I thought that bug was in some release prior to 
7.4.6. Does the bug allow it to show a vacuum taking place but not do 
it?

Cheers,
Steve



view thread (19+ messages)  latest in thread

Message-ID: <200503171637.16975.scrawford@pinpointresearch.com>
Permalink:  ../200503171637.16975.scrawford@pinpointresearch.com/
Also on:    postgresql.org/message-id/200503171637.16975.scrawford@pinpointresearch.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: scrawford@pinpointresearch.com
  Subject: Re: Excessive growth of pg_attribute and other system tables
  In-Reply-To: <200503171637.16975.scrawford@pinpointresearch.com>
  References: <200503171515.38214.scrawford@pinpointresearch.com> <28709.1111103484@sss.pgh.pa.us> <200503171637.16975.scrawford@pinpointresearch.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