| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | johnlumby(at)hotmail(dot)com |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #14098: misleading message "out of shared memory" when lock table space exhausted |
| Date: | 2016-04-18 17:37:11 |
| Message-ID: | 320.1461001031@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
johnlumby(at)hotmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-04-18 17:42:55 | Re: BUG #14099: Altering temporary sequence in session has no effect |
| Previous Message | imraan | 2016-04-18 17:13:47 | BUG #14099: Altering temporary sequence in session has no effect |