Re: shm

From: Scott Ribe <scott_ribe(at)elevated-dev(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-admin <pgsql-admin(at)postgresql(dot)org>
Subject: Re: shm
Date: 2020-03-06 14:06:50
Message-ID: 7A7FD3C8-763B-4B29-A6FC-720D4DDB6EB7@elevated-dev.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

> On Mar 5, 2020, at 7:51 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

  • Re: shm at 2020-03-05 14:51:45 from Tom Lane

Responses

  • Re: shm at 2020-03-06 15:34:41 from Tom Lane

Browse pgsql-admin by date

  From Date Subject
Next Message Tom Lane 2020-03-06 15:34:41 Re: shm
Previous Message Scott Ribe 2020-03-06 14:03:17 Re: shm