Re: Vacuum stops with misleading max_fsm_pages error - Mailing list pgsql-admin

From Tom Lane
Subject Re: Vacuum stops with misleading max_fsm_pages error
Date
Msg-id 11516.1176762986@sss.pgh.pa.us
Whole thread Raw
In response to Re: Vacuum stops with misleading max_fsm_pages error  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-admin
"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

pgsql-admin by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: Vacuum stops with misleading max_fsm_pages error
Next
From: "Matthew T. O'Connor"
Date:
Subject: Re: Vacuum stops with misleading max_fsm_pages error