| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
| Cc: | Thuc Nguyen Canh <thucnguyencanh(at)gmail(dot)com>, Forums postgresql <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Query error: could not resize shared memory segment |
| Date: | 2018-01-03 05:34:04 |
| Message-ID: | 15383.1514957644@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> writes:
> On Wed, Jan 3, 2018 at 6:13 PM, Thuc Nguyen Canh
> <thucnguyencanh(at)gmail(dot)com> wrote:
>> mount | grep /dev/shm
>> => shm on /dev/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=65536k)
> Bingo. Somehow your container tech is limiting shared memory.
If this is a common setup, maybe we're going to need a new section
under or near
https://www.postgresql.org/docs/current/static/kernel-resources.html#SYSVIPC
It's pretty annoying to have sweated blood to get out from under the
kernel's chosen-at-random SysV IPC limits, only to run into container
tmpfs limits that seem equally chosen with the aid of a dartboard.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thuc Nguyen Canh | 2018-01-03 05:50:50 | Re: Query error: could not resize shared memory segment |
| Previous Message | Thomas Munro | 2018-01-03 05:16:22 | Re: Query error: could not resize shared memory segment |