From: Tom Lane <tgl@sss.pgh.pa.us>
To: Wells Oliver <wells.oliver@gmail.com>
cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: Understanding was terminated by signal 9: Killed
In-reply-to: 
 <CAOC+FBWu83+5aiwgzGig38xVQzrWKP1obytTT=P=2r3UgQFiug@mail.gmail.com>
References: 
 <CAOC+FBWu83+5aiwgzGig38xVQzrWKP1obytTT=P=2r3UgQFiug@mail.gmail.com>
Comments: In-reply-to Wells Oliver <wells.oliver@gmail.com>
	message dated "Tue, 19 Oct 2021 14:42:15 -0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2009136.1634680908.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Tue, 19 Oct 2021 18:01:48 -0400
Message-ID: <2009137.1634680908@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2009137.1634680908%40sss.pgh.pa.us>
Precedence: bulk

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 c=
an
> 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-ME=
MORY-OVERCOMMIT