| 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:03:17 |
| Message-ID: | 8F5C3CAB-FAFA-4F3D-AAA0-8E9C3A0DEC45@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:
>
> Scott Ribe <scott_ribe(at)elevated-dev(dot)com> writes:
>> What is POSIX shared memory used for anymore?
>
> 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.
>
> regards, tom lane
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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Ribe | 2020-03-06 14:06:50 | Re: shm |
| Previous Message | Mark Steben | 2020-03-06 13:50:03 | Re: conflicting lock request message |