Re: BUG #14098: misleading message "out of shared memory" when lock table space exhausted - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #14098: misleading message "out of shared memory" when lock table space exhausted
Date
Msg-id 320.1461001031@sss.pgh.pa.us
Whole thread Raw
In response to BUG #14098: misleading message "out of shared memory" when lock table space exhausted  (johnlumby@hotmail.com)
List pgsql-bugs
johnlumby@hotmail.com writes:
> If postgresql exhausts the space reserved for locks,  whose size is defined
> by
>  max_locks_per_transaction * (max_connections + max_prepared_transactions)
> locks,
> then it issues this message :

> psql: FATAL:  out of shared memory
> HINT:  You might need to increase max_locks_per_transaction.

> The words "out of shared memory" are misleading  (and ungrammatical,  and
> somewhat contradict the HINT).

They are also correct, unlike your proposed revision.  There isn't a hard
separation of lock table space from the generally-available shared memory
pool.

            regards, tom lane

pgsql-bugs by date:

Previous
From: imraan@techie.com
Date:
Subject: BUG #14099: Altering temporary sequence in session has no effect
Next
From: Tom Lane
Date:
Subject: Re: BUG #14099: Altering temporary sequence in session has no effect