pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Steve Crawford <scrawford@pinpointresearch.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Excessive growth of pg_attribute and other system tables
Date: Thu, 17 Mar 2005 20:32:48 -0500
Message-ID: <29316.1111109568@sss.pgh.pa.us> (raw)
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>

Steve Crawford <scrawford@pinpointresearch.com> writes:
> On Thursday 17 March 2005 3:51 pm, Tom Lane wrote:
>> Do you have the FSM settings set large enough to account for all
>> the free space?

> max_fsm_pages = 20000
> max_fsm_relations = 1000

That doesn't sound like nearly enough pages for a 2G database.
20000 * 8K = 160MB, so if more than 10% of the pages in your DB
are dirty you are going to be leaking free space.  You probably
want max_fsm_pages up around 250,000.

> 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?

That would be a good plan too.

> 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?

I don't recall the details of the changes; you could look at the CVS
logs to see what got fixed when.  But in any case I think we see the
main problem: max_fsm_pages too small.

			regards, tom lane



view thread (19+ messages)  latest in thread

Message-ID: <29316.1111109568@sss.pgh.pa.us>
Permalink:  ../29316.1111109568@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/29316.1111109568@sss.pgh.pa.us

 · 

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: tgl@sss.pgh.pa.us, scrawford@pinpointresearch.com
  Subject: Re: Excessive growth of pg_attribute and other system tables
  In-Reply-To: <29316.1111109568@sss.pgh.pa.us>
  References: <200503171515.38214.scrawford@pinpointresearch.com> <28709.1111103484@sss.pgh.pa.us> <200503171637.16975.scrawford@pinpointresearch.com> <29316.1111109568@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