| From: | Francisco Olarte <folarte(at)peoplecall(dot)com> |
|---|---|
| To: | Christian Schröder <christian(dot)schroeder(at)wsd(dot)com> |
| Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>, Eric Wong <eric(dot)wong(at)wsd(dot)com> |
| Subject: | Re: Memory issues with PostgreSQL 15 |
| Date: | 2024-05-28 17:14:49 |
| Message-ID: | CA+bJJbyzFdr1i1Yarqt=JnsN0WUg+veRvYZC1+kaYnWFGjiYRw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi Christian:
On Tue, 28 May 2024 at 18:40, Christian Schröder
<christian(dot)schroeder(at)wsd(dot)com> wrote:
> <2024-05-21 11:34:46 CEST - mailprocessor> ERROR: could not resize shared memory segment "/PostgreSQL.2448337832" to 182656 bytes: No space left on device
This hints at some shm function getting an ENOSPC: Coupled with...
> I thought this could all be related to our "shared_buffers" setting, so I increased it to 8 GB. This almost immediately (after a few minutes) gave me these errors:
A faster fail when increasing it I would start by checking your IPC
shared memory limits are ok, especially if you upgraded something in
the OS when going from 9 to 15, which seems likely.
IIRC in linux you can read them in /proc/sys/kernel/shm*, and they
were configured via sysctl.
Francisco Olarte.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2024-05-28 18:01:20 | Re: Pgpool with high availability |
| Previous Message | Kashif Zeeshan | 2024-05-28 16:54:22 | Re: Pgpool with high availability |