pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jim C. Nasby <jnasby@pervasive.com>
To: Robin Iddon <robin@edesix.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: 8.0.3 pg_autovacuum doesn't clear out stats table?
Date: Thu, 23 Feb 2006 17:58:29 -0600
Message-ID: <20060223235829.GP2068@pervasive.com> (raw)
In-Reply-To: <43FE4A1A.7050903@edesix.com>
References: <43FD7312.5080701@edesix.com>
	<20060223211835.GZ86022@pervasive.com>
	<43FE4A1A.7050903@edesix.com>

On Thu, Feb 23, 2006 at 11:49:46PM +0000, Robin Iddon wrote:
> Jim C. Nasby wrote:
> 
> >Please upgrade.
> >
> >Are you running with the default FSM settings? I'm guessing that
> >pg_statistics has just gotten so large that it's blowing out the FSM.
> >The last few lines from vacuumdb -av would verify that...
> > 
> >
> Jim,
> 
> I am running this in a critical production environment, so I would like 
> to understand whether upgrading is my only option before I do it (I'll 
> need to do some testing first, then organise downtime, etc. - I will do 
> it if required, but would rather a workaround!).  If I do upgrade, I 
> assume you mean upgrade to the current 8.1.x release?

Well, as I mentioned elsewhere, there are some reasons to upgrade to
8.1.x. But no, my comment was specifically about upgrading to the latest
8.0 release. There have been both security and data-loss fixes that you
really should get.

> Yes, I am running with the default FSM settings.
> 
> Here is the output from vacuumdb -v gems (I ran it against my tiny test 
> database, not the production database right now, but remember that even 
> this tiny test database had an enormous pg_statistic table):
> 
> <snip> this is the last few lines as requested
> INFO:  free space map: 182 relations, 25120 pages stored; 98272 total 
> pages needed
> DETAIL:  Allocated FSM size: 1000 relations + 20000 pages = 182 kB 
> shared memory.
> <snip>

You need 100k pages minimum here.

> I don't actually understand exactly what this is telling me though!

Take a look at
http://www.pervasivepostgres.com/lp/newsletters/2005/Insights_opensource_Nov.asp#3
It's a good overview of the FSM, how it works, and how to understand
vacuum verbose output. Though, I guess my opinion is biased since I
wrote it... ;)
-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461



view thread (13+ messages)  latest in thread

Message-ID: <20060223235829.GP2068@pervasive.com>
Permalink:  ../20060223235829.GP2068@pervasive.com/
Also on:    postgresql.org/message-id/20060223235829.GP2068@pervasive.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: jnasby@pervasive.com, robin@edesix.com
  Subject: Re: 8.0.3 pg_autovacuum doesn't clear out stats table?
  In-Reply-To: <20060223235829.GP2068@pervasive.com>
  References: <43FD7312.5080701@edesix.com> <20060223211835.GZ86022@pervasive.com> <43FE4A1A.7050903@edesix.com> <20060223235829.GP2068@pervasive.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