| From: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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:05:38 |
| Message-ID: | CAEepm=2+rSCHjoY4bYD6taiSp-yUexJ6xHBLacCddH-Dk3sx=w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Jan 3, 2018 at 5:39 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> writes:
>> So you have 16GB of RAM and here we're failing to posix_fallocate()
>> 50MB (actually we can't tell if it's the ftruncate() or
>> posix_fallocate() call that failed, but the latter seems more likely
>> since the former just creates a big hole in the underlying tmpfs
>> file). Can you share the query plan (EXPLAIN SELECT ...)?
>
> I wonder if OP is running with a tmpfs size setting that's less than
> the traditional Linux default of half of physical RAM size.
Hmm. Canh, can you please share the output of the following commands?
mount | grep /dev/shm
du -hs /dev/shm
df /dev/shm
--
Thomas Munro
http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thuc Nguyen Canh | 2018-01-03 05:13:51 | Re: Query error: could not resize shared memory segment |
| Previous Message | Thuc Nguyen Canh | 2018-01-03 04:49:39 | Re: Query error: could not resize shared memory segment |