pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Joshua D. Drake <jd@commandprompt.com>
To: Kieran Cooper, Lyris UK <kieran@lyris.co.uk>
Cc: pgsql-admin@postgresql.org
Subject: Re: Vacuum stops with misleading max_fsm_pages error
Date: Mon, 16 Apr 2007 15:08:54 -0700
Message-ID: <4623F3F6.8040408@commandprompt.com> (raw)
In-Reply-To: <001901c78071$9a9a1f00$0b02a8c0@KieranX15>
References: <001901c78071$9a9a1f00$0b02a8c0@KieranX15>

Kieran Cooper, Lyris UK wrote:
> Hi there,
> 
> We're managing a database on version 8.2.3 (running Lyris ListManager 
> email software). I ran a 'vacuum analyze full verbose' (we haven't been 
> able to get autovacuum to work properly on Lyris installs so we need to 
> run a full vacuum every week or so, and we'd been doing some work on 
> this machine so it needed it)

Why not just set up a regular vacuum to run twice a day?


. It ran happily for quite a while - about
> 2 thirds of the way through the database - but then ended with the lines
> 
> INFO:  free space map contains 20914 pages in 61 relations
> DETAIL:  A total of 14992 page slots are in use (including overhead).
> 14992 page slots are required to track all free space.
> Current limits are:  900000 page slots, 6000 relations, using 5659 kB.
> 
> This happens (at more or less the same point but with slightly different 
> figures) each time I try to run this command. It also happens even if I 
> only do vacuum verbose.

I am not sure what your question is. The above looks perfectly reasonable.

> 
> I can vacuum individual tables quite happily but I'm not sure I can 
> manage to do all of them individually.

See comment above about using a vacuum/vacuum analyze twice a day.

> 
> As you see, I've upped the page slots and relations (there are 131 
> tables in the database in total) and it seems to me like there is more 
> than enough.

Yep.

> 
> Any ideas would be gratefully received!

...? The only thing I would say is that you are entirely too many 
max_fsm_pages and max_fsm_relations. I would drop it back dow:

max_fsm_pages = 100000
max_fsm_relations = 1000

But that doesn't really answer your question as much as state that you 
don't need as much as you have.

Sincerely,

Joshua D. Drake



> Thanks
> Kieran Cooper
> Lyris UK
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
> 


-- 

       === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive  PostgreSQL solutions since 1997
              http://www.commandprompt.com/

Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/




view thread (7+ messages)  latest in thread

Message-ID: <4623F3F6.8040408@commandprompt.com>
Permalink:  ../4623F3F6.8040408@commandprompt.com/
Also on:    postgresql.org/message-id/4623F3F6.8040408@commandprompt.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 using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: jd@commandprompt.com, kieran@lyris.co.uk
  Subject: Re: Vacuum stops with misleading max_fsm_pages error
  In-Reply-To: <4623F3F6.8040408@commandprompt.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