From: | Francisco Olarte <folarte(at)peoplecall(dot)com> |
---|---|
To: | Christian Schröder <christian(dot)schroeder(at)wsd(dot)com> |
Cc: | Muhammad Salahuddin Manzoor <salahuddin(dot)m(at)bitnine(dot)net>, pgsql-general <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-30 11:02:52 |
Message-ID: | CA+bJJbxT4S5hedrfBEzn2tDf650VLN8p6a6ey+QxSsctirtKBw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi christian:
On Thu, 30 May 2024 at 12:51, Christian Schröder
<christian(dot)schroeder(at)wsd(dot)com> wrote:
...
> I had already checked most of your points, but I double checked them now.
...
> Shared memory limits look good to me:
> # sudo sysctl -a | grep kernel.shm
> kernel.shmall = 18446744073692774399
> kernel.shmmax = 18446744073692774399
> kernel.shmmni = 4096
Bear in mind this is SysV shared memory. IIRC Pg uses POSIX shared
memory for shared buffers, which I think is backed normally in Linux
by files in a tmpfs mounted on /dev/shm. It still uses some amount of
SysV due to some special properties lacking from POSIX, for control
purposes, but only a little.
You could try "df -h /dev/shm" and "ls -lhR /dev/shm/" to see if you
have problems there.
Francisco Olarte.
From | Date | Subject | |
---|---|---|---|
Next Message | Alanoly Andrews | 2024-05-30 14:58:41 | ERROR: found xmin from before relfrozenxid; MultiXactid does no longer exist -- apparent wraparound |
Previous Message | Francisco Olarte | 2024-05-30 10:13:50 | Re: Memory issues with PostgreSQL 15 |