pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Joshua D. Drake <jd@commandprompt.com>
Cc: 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 18:36:26 -0400
Message-ID: <11516.1176762986@sss.pgh.pa.us> (raw)
In-Reply-To: <4623F3F6.8040408@commandprompt.com>
References: <001901c78071$9a9a1f00$0b02a8c0@KieranX15>
	<4623F3F6.8040408@commandprompt.com>

"Joshua D. Drake" <jd@commandprompt.com> writes:
> Kieran Cooper, Lyris UK wrote:
>> 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.

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

I think he's wondering why the second number is less than the first.
AFAICT that should be impossible after a VACUUM FULL, but there are
probably tables that haven't been touched by the VACUUM FULL --- stuff
in other databases being one obvious possibility.  As for the vacuum
not having done every table in the current database, did you run it
as superuser?

			regards, tom lane



view thread (7+ messages)  latest in thread

Message-ID: <11516.1176762986@sss.pgh.pa.us>
Permalink:  ../11516.1176762986@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/11516.1176762986@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-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, jd@commandprompt.com, kieran@lyris.co.uk
  Subject: Re: Vacuum stops with misleading max_fsm_pages error
  In-Reply-To: <11516.1176762986@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