Date: Tue, 22 Dec 2020 15:09:55 +0100
From: hubert depesz lubaczewski <depesz@depesz.com>
Sender: depesz@depesz.com
To: Sreejith P <sreejith@lifetrenz.com>
Cc: "pgsql-admin@lists.postgresql.org" <pgsql-admin@lists.postgresql.org>
Subject: Re: Memory Issues.
Message-ID: <20201222140955.GB23159@depesz.com>
Reply-To: depesz@depesz.com
References: 
 <PS2PR02MB283729A5CCA2EDA94E75E693F3DF0@PS2PR02MB2837.apcprd02.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: 
 <PS2PR02MB283729A5CCA2EDA94E75E693F3DF0@PS2PR02MB2837.apcprd02.prod.outlook.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Precedence: bulk

On Tue, Dec 22, 2020 at 07:32:04AM +0000, Sreejith P wrote:
> Dear All,
> 2020-12-21 23:59:32.869 +04 [16097] rptDBA@Ast-ReportDB LOG:  could not receive data from client: Connection timed out
> 2020-12-22 01:12:53.939 +04 [11961] rptDBA@Ast-ReportDB LOG:  could not receive data from client: Connection reset by peer
> 2020-12-22 01:23:08.832 +04 [30360] LOG:  server process (PID 17872) was terminated by signal 9: Killed

One of Pg processes (with PID 17872) was killed with signal 9 (sigkill).
It could be operator killing process, some automation, or so called
"oom killer".

Pg can't really do anything about being killed in this way, so you have
to track down what is issuing this kill signal, and disable it.

I'd suggest to try with system logs.

Best regards,

depesz