| From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> | 
|---|---|
| To: | "Kynn Jones" <kynnjo(at)gmail(dot)com> | 
| Cc: | "pgsql-general General" <pgsql-general(at)postgresql(dot)org> | 
| Subject: | Re: "Consider compacting this relation..." ??? | 
| Date: | 2008-02-28 23:34:40 | 
| Message-ID: | dcc563d10802281534u3076ea77mc969709818a9a655@mail.gmail.com | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-general | 
On Thu, Feb 28, 2008 at 3:14 PM, Kynn Jones <kynnjo(at)gmail(dot)com> wrote:
> I just ran VACUUM ANALYZE and got this warning I've never seen before:
>
>  WARNING:  relation "public.some_big_table" contains more than
> "max_fsm_pages" pages with useful free space
> HINT:  Consider compacting this relation or increasing the configuration
> parameter "max_fsm_pages".
>
>
> What does the hint mean by "compacting"?  What exactly must I do to compact
> this table?
Vacuum full
>  Also, at the end of the VACUUM ANALYZE run I get the NOTICE:
>
> NOTICE:  number of page slots needed (294528) exceeds max_fsm_pages (153600)
> HINT:  Consider increasing the configuration parameter "max_fsm_pages" to a
> value over 294528.
>
>
> What surprises me here is that even though I've never seen this notice
> before (and I've been running VACUUM ANALYZE a lot lately!), the number of
> page slots needed is almost twice as much as the value of max_fsm_pages.
> What could I have done since the last time I ran VACUUM ANALYZE (not more
> than 24 hours ago) to make this "page slot" requirement to shoot through the
> roof like this?
Lots of deletes or updates on the table.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sam Mason | 2008-02-29 00:00:20 | Re: WAL Log Size | 
| Previous Message | Scott Marlowe | 2008-02-28 23:32:52 | Re: LIMIT Question |