Hi christian:
On Thu, 30 May 2024 at 12:51, Christian Schröder
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 =
kernel.shmmax = 18446744073692774399
kernel.shmmni = 4096
Thanks,
Christian
From: Muhammad Salahuddin Manzoor
Sent: Wednesday, May 29, 2024 11:41 AM
To: Christian Schröder
Cc: pgsql-general ; Eric Wong
Subject: Re: Memory issues with PostgreSQL 15
[EXTERNAL]
Greetings,
The error message you
: pgsql-general@lists.postgresql.org; Eric Wong
Subject: Re: Memory issues with PostgreSQL 15
[EXTERNAL]
Hi Christian:
On Wed, 29 May 2024 at 00:59, Christian Schröder
wrote:
> Thank you for your advice. I used "ipcs" to get more readable information
> about the shared memory:
.
On Thu, 30 May 2024 at 09:37, Christian Schröder
wrote:
> Unfortunately, all disks have plenty of free space, so this can be ruled out
> as a reason.
> I will follow up on the other suggestions from the list.
Do not forget to check all mounted filesystems, not only disks.
Specially /dev/shm,
Il giorno mar 28 mag 2024 alle ore 18:40 Christian Schröder
ha scritto:
> Our PostgreSQL version is "PostgreSQL 15.5 on x86_64-pc-linux-gnu, compiled
> by gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44), 64-bit". The database server
> is a dedicated server with 15 GB RAM (and 4 cores, if this
=?utf-8?B?Q2hyaXN0aWFuIFNjaHLDtmRlcg==?= writes:
> # ipcs -m
> -- Shared Memory Segments
> keyshmid owner perms bytes nattch status
> 0x04000194 35 postgres 60056 19
> I am surprised to see this since I would have expected
t: Tuesday, May 28, 2024 7:15 PM
To: Christian Schröder
Cc: pgsql-general@lists.postgresql.org; Eric Wong
Subject: Re: Memory issues with PostgreSQL 15
[EXTERNAL]
Hi Christian:
On Tue, 28 May 2024 at 18:40, Christian Schröder
wrote:
> <2024-05-21 11:34:46 CEST - mailprocessor> ERROR
Greetings,
The error message you encountered, "could not fork autovacuum worker
process: Cannot allocate memory," indicates that your PostgreSQL server
attempted to start an autovacuum worker process but failed because the
system ran out of memory.
Steps to verify.
1 Check system available
Hi Christian:
On Wed, 29 May 2024 at 00:59, Christian Schröder
wrote:
> Thank you for your advice. I used "ipcs" to get more readable information
> about the shared memory:
...
> As far as I understand, there is no upper limit to the size of the shared
> memory. The database only holds a
Hi Christian:
On Tue, 28 May 2024 at 18:40, Christian Schröder
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
Hi all,
We migrated from PostgreSQL 9.4 to PostgreSQL 15 a while ago. Since then, we
have a lot of memory issues in our QA environment (which is a bit tense in
resources). We did not have these problems before the migration, and we do not
have them in our production environment, which has a lot
11 matches
Mail list logo
