Re: Understanding was terminated by signal 9: Killed - Mailing list pgsql-admin

From Tom Lane
Subject Re: Understanding was terminated by signal 9: Killed
Date
Msg-id 2009137.1634680908@sss.pgh.pa.us
Whole thread Raw
In response to Understanding was terminated by signal 9: Killed  (Wells Oliver <wells.oliver@gmail.com>)
Responses Re: Understanding was terminated by signal 9: Killed  (John Scalia <jayknowsunix@gmail.com>)
List pgsql-admin
Wells Oliver <wells.oliver@gmail.com> writes:
> In an RDS instance with 16GB RAM, I ran a long query which started by
> setting temp_buffers to 16GB, so I think I plum ran out of memory, but can
> anyone point me in a different direction if the following log messages
> indicate something else is awry?

Yeah, this:

> 2021-10-19 21:10:37 UTC::@:[24752]:LOG:  server process (PID 25813) was
> terminated by signal 9: Killed

almost certainly indicates the Linux OOM killer at work.  If you were
running your own system I'd point you to [1], but I doubt that RDS
lets you put your hands on the relevant knobs.

            regards, tom lane

[1] https://www.postgresql.org/docs/current/kernel-resources.html#LINUX-MEMORY-OVERCOMMIT



pgsql-admin by date:

Previous
From: Wells Oliver
Date:
Subject: Understanding was terminated by signal 9: Killed
Next
From: John Scalia
Date:
Subject: Re: Understanding was terminated by signal 9: Killed