pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Steve Crawford <scrawford@pinpointresearch.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: Matthew T. O'Connor <matthew@zeut.net>
Cc: pgsql-admin@postgresql.org
Subject: Re: Excessive growth of pg_attribute and other system tables
Date: Mon, 21 Mar 2005 12:35:22 -0800
Message-ID: <200503211235.22731.scrawford@pinpointresearch.com> (raw)
In-Reply-To: <1219.1111434030@sss.pgh.pa.us>
References: <200503171515.38214.scrawford@pinpointresearch.com>
	<423F17D7.7040904@zeut.net>
	<1219.1111434030@sss.pgh.pa.us>

On Monday 21 March 2005 11:40 am, Tom Lane wrote:

> However, given that there are 9334 tuples in 82282 pages, I'd say
> that autovacuum has already failed Steve rather badly :-(.  There
> shouldn't be more than a couple hundred pages given that number of
> rows.  Perhaps the FSM settings are too small?

Yup, we've pretty well established that my fsm settings were way too 
low. I've bumped them up:
max_fsm_relations from 1,000 to 3,000
max_fsm_pages from 20,000 to 1,000,000

The slight expenditure of a few meg of RAM on a 4G ram machine will 
hurt me far less than the incomplete vacuums. I have to schedule some 
low-volume time to restart the server and vacum-full before I'll see 
the result.

Just to make sure I'm understanding things correctly this time...I 
originally (mis)understood these as settings related to resources 
used _during_ vacuuming. My current understanding is that they are 
basically pointers that track what space is available for reclamation 
by vaccum and that the amount of fsm resources required depends on 
both frequency of vacuums and volume of updates/deletes.

Questions:

1) Is my revised understanding correct?

And if the answer to 1 is yes...

2) What happens with all that free-space information at server restart 
(ie. does a server restart lead to dead-tuple leakage)?

3) Is (or should) there be logging of the fact that a server has run 
out of resources to track dead space?

4) Is there a way to query what proportion of the fsm resources are in 
use and would access to that info be useful to the autovacuum daemon 
or a system tuner?

Cheers,
Steve




view thread (19+ messages)  latest in thread

Message-ID: <200503211235.22731.scrawford@pinpointresearch.com>
Permalink:  ../200503211235.22731.scrawford@pinpointresearch.com/
Also on:    postgresql.org/message-id/200503211235.22731.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, tgl@sss.pgh.pa.us, matthew@zeut.net
  Subject: Re: Excessive growth of pg_attribute and other system tables
  In-Reply-To: <200503211235.22731.scrawford@pinpointresearch.com>
  References: <200503171515.38214.scrawford@pinpointresearch.com> <423F17D7.7040904@zeut.net> <1219.1111434030@sss.pgh.pa.us> <200503211235.22731.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