Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: John Scalia <jayknowsunix@gmail.com>
Mime-Version: 1.0 (1.0)
Subject: Re: Understanding was terminated by signal 9: Killed
Date: Tue, 19 Oct 2021 19:12:04 -0400
Message-Id: <AEEF347B-39EC-41FC-8AC9-2AFA54F71391@gmail.com>
References: <2009137.1634680908@sss.pgh.pa.us>
Cc: Wells Oliver <wells.oliver@gmail.com>,
 pgsql-admin <pgsql-admin@postgresql.org>
In-Reply-To: <2009137.1634680908@sss.pgh.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/AEEF347B-39EC-41FC-8AC9-2AFA54F71391%40gmail.com>
Precedence: bulk

You could always change the size of the RDS instance to something larger tha=
n what it currently is running, even just temporarily.

Sent from my iPad

> On Oct 19, 2021, at 6:01 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>=20
> =EF=BB=BFWells 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 ca=
n
>> anyone point me in a different direction if the following log messages
>> indicate something else is awry?
>=20
> Yeah, this:
>=20
>> 2021-10-19 21:10:37 UTC::@:[24752]:LOG:  server process (PID 25813) was
>> terminated by signal 9: Killed
>=20
> 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.
>=20
>            regards, tom lane
>=20
> [1] https://www.postgresql.org/docs/current/kernel-resources.html#LINUX-ME=
MORY-OVERCOMMIT
>=20
>=20