| From: | Thuc Nguyen Canh <thucnguyencanh(at)gmail(dot)com> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Forums postgresql <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Query error: could not resize shared memory segment |
| Date: | 2018-01-03 05:50:50 |
| Message-ID: | CAG903PpRcP7SgW1H72GF5Ukjd9E_8amsUX2YpKCNQNCvD=_O2g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Thank you Thomas,
I make it work with extra setting --shm-size=1g in my docker run script.
On Wed, Jan 3, 2018 at 12:16 PM, Thomas Munro
<thomas(dot)munro(at)enterprisedb(dot)com> wrote:
> On Wed, Jan 3, 2018 at 6:13 PM, Thuc Nguyen Canh
> <thucnguyencanh(at)gmail(dot)com> wrote:
>> And here is the result from postgres container:
>>
>> 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. That
> error is working as designed. You could figure out how to fix the
> mount options, or you could disable parallelism with
> max_parallel_workers_per_gather = 0.
>
> --
> Thomas Munro
> http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Igal Sapir | 2018-01-03 06:18:34 | Re: Returning Values from INSERT ON CONFLICT DO NOTHING |
| Previous Message | Tom Lane | 2018-01-03 05:34:04 | Re: Query error: could not resize shared memory segment |