| From: | "Arthur Ward" <award(at)dominionsciences(dot)com> |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | 7.4RC2 PANIC: insufficient room in FSM |
| Date: | 2003-11-25 17:37:07 |
| Message-ID: | 42893.68.62.129.152.1069781827.squirrel@award.gotdns.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
I was a bit stunned last night when I found this in the server logs for a
7.4RC2 installation:
Nov 24 20:37:18 x pg_autovacuum: [2003-11-24 08:37:18 PM] Performing:
VACUUM ANALYZE "clients"."x"
Nov 24 20:37:19 x postgres: [13904] PANIC: insufficient room in FSM
Nov 24 20:37:19 x postgres: STATEMENT: VACUUM ANALYZE "clients"."x"
Following this is of course the fallout of backends shutting down and PG
recycling itself with no other problems. Did I miss something along the
way about the FSM needing to be sufficiently large to hold all free pages
no matter what?
I plan to bump up the FSM size anyhow (perhaps tonight I can get some FSM
stats from manually vacuuming), but my gosh, that's some bad behavior for
a presumably minor situation. IMO, that's a significant bug.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-11-25 18:46:56 | Re: 7.4RC2 PANIC: insufficient room in FSM |
| Previous Message | Peter Eisentraut | 2003-11-25 14:37:51 | Re: [PATCHES] (Modified) Patch request for PostgreSQL 7.4 for HP-UX |