Re: Fresh Restore - relation contains more than "max_fsm_pages" - Mailing list pgsql-general

From Craig Ringer
Subject Re: Fresh Restore - relation contains more than "max_fsm_pages"
Date
Msg-id 4E322F54.5020507@postnewspapers.com.au
Whole thread Raw
In response to Fresh Restore - relation contains more than "max_fsm_pages"  ("Maton, Brett" <matonb@ltresources.co.uk>)
Responses Re: Fresh Restore - relation contains more than "max_fsm_pages"
List pgsql-general
On 28/07/11 18:13, Maton, Brett wrote:
> postgresql v8.3.14
>
> Can anyone help me identify why a vacuum on clean pg_restore database
> would give this warning?
> I've been told that the database was restored and not been touched
> since, i.e. no inserts / updates or deletes.  So I'm curious as to why
> it appears to have been created with excessive "holes".

Maybe a non-default FILLFACTOR was set on some tables/indexes?

Or - especially if restore was done as schema followed by data rather
than all in one - the index creation and subsequent updates freed too
many pages?

Personally, I'd recommend moving to 8.4 or above, where you no longer
need worry about the free space map at all.

--
Craig Ringer

pgsql-general by date:

Previous
From: Craig Ringer
Date:
Subject: Re: How to implement autostart of postgres?
Next
From: "Maton, Brett"
Date:
Subject: Re: Fresh Restore - relation contains more than "max_fsm_pages"