Re: Fresh Restore - relation contains more than "max_fsm_pages"

From: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
To: "Maton, Brett" <matonb(at)ltresources(dot)co(dot)uk>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Fresh Restore - relation contains more than "max_fsm_pages"
Date: 2011-07-29 03:56:04
Message-ID: 4E322F54.5020507@postnewspapers.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Craig Ringer 2011-07-29 04:38:23 Re: How to implement autostart of postgres?
Previous Message Tom Lane 2011-07-29 02:50:54 Re: issue with pg_restore