From: Tom Lane <tgl@sss.pgh.pa.us>
To: Scott Ribe <scott_ribe@elevated-dev.com>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: shm
Date: Fri, 06 Mar 2020 10:34:41 -0500
Message-ID: <23559.1583508881@sss.pgh.pa.us> (raw)
In-Reply-To: <7A7FD3C8-763B-4B29-A6FC-720D4DDB6EB7@elevated-dev.com>
References: <565DBAD4-E79D-4EE0-89C4-ABE33AD0C0A7@elevated-dev.com>
<1582.1583419905@sss.pgh.pa.us>
<7A7FD3C8-763B-4B29-A6FC-720D4DDB6EB7@elevated-dev.com>
Scott Ribe <scott_ribe@elevated-dev.com> writes:
>> On Mar 5, 2020, at 7:51 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> We still allocate a small shm block as a means of counting live backends
>> (since the SysV spec includes an "nattch" count but mmap'd segments do
>> not provide that info). Should only be ~50 bytes though.
> I recreated the error so I could post it here:
> ERROR 53100 (disk_full) could not resize shared memory segment "/PostgreSQL.935653392" to 1048576 bytes: No space left on device
Oh, if it's trying to resize then this is dynamic shared memory, not
the small static block. On most platforms we use POSIX shm_open() for
that purpose, not SysV-style shm ... what have you got
dynamic_shared_memory_type set to?
It could be that the space limit applies to both APIs anyway, in which
case your choices are to raise the limit or disable parallel query.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, scott_ribe@elevated-dev.com
Subject: Re: shm
In-Reply-To: <23559.1583508881@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox