pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Josh Berkus <josh@agliodbs.com>
Cc: Tambet Matiisen <t.matiisen@aprote.ee>
Cc: Bill Chandler <billybobc1210@yahoo.com>
Cc: pgsql-perform <pgsql-performance@postgresql.org>
Subject: Re: Question on REINDEX
Date: Tue, 19 Apr 2005 12:24:02 -0400
Message-ID: <22304.1113927842@sss.pgh.pa.us> (raw)
In-Reply-To: <200504190857.16634.josh@agliodbs.com>
References: <A66A11DBF5525341AEF6B8DE39CDE77008806E@black.aprote.com>
	<200504190857.16634.josh@agliodbs.com>

Josh Berkus <josh@agliodbs.com> writes:
>> select count(1), sum(relpages) from pg_class where relkind in
>> ('r','i','t')

> Well, if you do that for all databases in the cluster, it's the number you 
> start with.  However, setting FSM_pages to that would be assuming that you 
> excpected 100% of the rows to be replaced by UPDATES or DELETEs before you 
> ran VACUUM.   I generally run VACUUM a little sooner than that.

Not at all.  What it says is that you expect 100% of the pages to have
useful amounts of free space, which is a *much* weaker criterion.

I think you can usually get away with setting max_fsm_pages to less than
your actual disk footprint, but I'm not sure how much less.  It'd
probably depend a lot on your usage pattern --- for instance,
insert-only history tables don't need any FSM space.

			regards, tom lane



view thread (12+ messages)  latest in thread

Message-ID: <22304.1113927842@sss.pgh.pa.us>
Permalink:  ../22304.1113927842@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/22304.1113927842@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 using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: tgl@sss.pgh.pa.us, josh@agliodbs.com, t.matiisen@aprote.ee, billybobc1210@yahoo.com
  Subject: Re: Question on REINDEX
  In-Reply-To: <22304.1113927842@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