[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-admin
Subject:    Re: Terminating connection because of crash of another server process
From:       Laurenz Albe <laurenz.albe () cybertec ! at>
Date:       2023-09-29 9:27:33
Message-ID: 428f8ffe02b21f97f48887a2c6c97dd893cdbd8f.camel () cybertec ! at
[Download RAW message or body]

On Fri, 2023-09-29 at 11:21 +0300, Deo Felix wrote:
> Please find the screenshot of =C2=A0error from the log file=C2=A0=C2=A0po=
stgresqlerror.png

It is really amazing how much effort you make *not* to share
any relevant information with us.  But there is finally some
interesting message hidden in your image:

 server process (PID 14257) was terminated by signal 9: Killed

Since I don't expect that random users on your server machine
go around "kill -9"-ing PostgreSQL processes, it is very likely
that PostgreSQL is crashed by the Linux out-of-memory killer.

You should disable memory overcommit, see
https://www.postgresql.org/docs/current/kernel-resources.html#LINUX-MEMORY-=
OVERCOMMIT

Then you will start getting "out of memory" errors instead of
crashes.  To combat these, reduce the memory usage parameters,
mostly "work_mem", or reduce the number of active database sessions
by using a connection pool.

Yours,
Laurenz Albe


[prev in list] [next in list] [prev in thread] [next in thread]