| Lists: | Postg토토 사이트 추천SQL : Postg토토 사이트 추천SQL 메일 링리스트 : 2016-04-18 이후 PGSQL-BUGS 17:37 |
|---|
| From: | johnlumby(at)hotmail(dot)com |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | BUG #14098: misleading message "out of shared memory" when lock table space exhausted |
| Date: | 2016-04-18 16:46:48 |
| Message-ID: | 20160418164648.26012.40241@wrigleys.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 14098
Logged by: John Lumby
Email address: johnlumby(at)hotmail(dot)com
PostgreSQL version: 9.5.2
Operating system: linux 64-bit
Description:
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).
Shared mem space is not exhausted, lock table space is exhausted.
Please change the message to
psql: FATAL: lock table space is exhausted
HINT: You might need to increase max_locks_per_transaction.
I believe all cases of this msg are in
src/backend/storage/lmgr/lock.c
| 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 |
| Lists: | Postg토토 사이트 추천SQL : Postg토토 사이트 추천SQL 메일 링리스트 : 2016-04-18 이후 PGSQL-BUGS 17:37 |
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