pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Scott Ribe <scott_ribe@elevated-dev.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: shm
Date: Fri, 6 Mar 2020 07:06:50 -0700
Message-ID: <7A7FD3C8-763B-4B29-A6FC-720D4DDB6EB7@elevated-dev.com> (raw)
In-Reply-To: <1582.1583419905@sss.pgh.pa.us>
References: <565DBAD4-E79D-4EE0-89C4-ABE33AD0C0A7@elevated-dev.com>
	<1582.1583419905@sss.pgh.pa.us>

> 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

So something is using shared memory, and wants 1MB chunks. What could that be?

This is on PG 11.7






view thread (7+ messages)  latest in thread

Message-ID: <7A7FD3C8-763B-4B29-A6FC-720D4DDB6EB7@elevated-dev.com>
Permalink:  ../7A7FD3C8-763B-4B29-A6FC-720D4DDB6EB7@elevated-dev.com/
Also on:    postgresql.org/message-id/7A7FD3C8-763B-4B29-A6FC-720D4DDB6EB7@elevated-dev.com

 · 

reply

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: scott_ribe@elevated-dev.com, tgl@sss.pgh.pa.us
  Subject: Re: shm
  In-Reply-To: <7A7FD3C8-763B-4B29-A6FC-720D4DDB6EB7@elevated-dev.com>

* 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