Re: 7.4RC2 PANIC: insufficient room in FSM

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Arthur Ward" <award(at)dominionsciences(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: 7.4RC2 PANIC: insufficient room in FSM
Date: 2003-11-25 18:46:56
Message-ID: 410.1069786016@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"Arthur Ward" <award(at)dominionsciences(dot)com> writes:
> 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

We have seen reports of similar things in situations where the real
problem was that the lock table had gotten too big --- is it possible
that you had something going on in parallel that would have acquired
lots of locks? If so, raising max_locks_per_transaction should avoid
the problem.

I'll look at whether we couldn't downgrade the failure to something
less than a PANIC, too ...

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2003-11-25 19:11:24 Re: inner query bug
Previous Message Arthur Ward 2003-11-25 17:37:07 7.4RC2 PANIC: insufficient room in FSM