| From: | hubert depesz lubaczewski <depesz(at)depesz(dot)com> |
|---|---|
| To: | Sreejith P <sreejith(at)lifetrenz(dot)com> |
| Cc: | "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Memory Issues. |
| Date: | 2020-12-22 14:09:55 |
| Message-ID: | 20201222140955.GB23159@depesz.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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(at)Ast-ReportDB LOG: could not receive data from client: Connection timed out
> 2020-12-22 01:12:53.939 +04 [11961] rptDBA(at)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Ribe | 2020-12-22 14:50:32 | Re: Memory Issues. |
| Previous Message | Sreejith P | 2020-12-22 07:32:04 | Memory Issues. |