Message-ID: <428f8ffe02b21f97f48887a2c6c97dd893cdbd8f.camel@cybertec.at>
Subject: Re: Terminating connection because of crash of another server
 process
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Deo Felix <deofelix9@gmail.com>, Deepak Goel <deicool@gmail.com>
Cc: Scott Ribe <scott_ribe@elevated-dev.com>, Pgsql-admin
	 <pgsql-admin@lists.postgresql.org>
Date: Fri, 29 Sep 2023 11:27:33 +0200
In-Reply-To: 
 <CALW=F4MU2YL5mJTTwk7cfBAW7tUNrb+WvRKSvwHZCR=vu8kOyg@mail.gmail.com>
References: 
	<CALW=F4P3RVv67vn665eLy5AZ2EXSJ5ET-+f3edwSKt8ZL_=qxA@mail.gmail.com>
	 <78b8abef6c84c173aa1a5498cb3907db79d8593a.camel@cybertec.at>
	 <3DEB744B-A312-427A-8644-7B16BD60419A@elevated-dev.com>
	 <DB8P194MB0616CA8A36B3363FFE19B59EA2C2A@DB8P194MB0616.EURP194.PROD.OUTLOOK.COM>
	 <09FDA966-9E9D-4F52-8B4D-0A9C2283DA3A@elevated-dev.com>
	 <CALW=F4Mg79ASxRSnFiKNM8WcB4CLLkQzPdSvGVnrkDi62sJX7Q@mail.gmail.com>
	 <CFD4218D-C2D7-4EE4-82E2-D8336B5FA680@elevated-dev.com>
	 <CALW=F4O5EPxRchWe43ExhQps6UngN-6+vHcKrhmtph_L+rgL_w@mail.gmail.com>
	 <CA+b7NVVTCf_5E-qhMQDouarjTzVzMmaBkV=u0Lh3fVbMa=apoA@mail.gmail.com>
	 <CALW=F4NoG7MYuF=DWxC8mGUhfE0ziP+sa6+Wyjs7wg_r1OAyFQ@mail.gmail.com>
	 <CA+b7NVWN_-oQ3-O4d2T0sm5E7QQTK6+5fHi=a_kaKShoO+bKsA@mail.gmail.com>
	 <CALW=F4MU2YL5mJTTwk7cfBAW7tUNrb+WvRKSvwHZCR=vu8kOyg@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.48.4 (3.48.4-1.fc38) 
MIME-Version: 1.0
Archived-At: 
 <https://www.postgresql.org/message-id/428f8ffe02b21f97f48887a2c6c97dd893cdbd8f.camel%40cybertec.at>
Precedence: bulk

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