From: John Scalia <jayknowsunix@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Wells Oliver <wells.oliver@gmail.com>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
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> (raw)
In-Reply-To: <2009137.1634680908@sss.pgh.pa.us>
References: <2009137.1634680908@sss.pgh.pa.us>
You could always change the size of the RDS instance to something larger than 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:
>
> 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
>
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: jayknowsunix@gmail.com, tgl@sss.pgh.pa.us, wells.oliver@gmail.com
Subject: Re: Understanding was terminated by signal 9: Killed
In-Reply-To: <AEEF347B-39EC-41FC-8AC9-2AFA54F71391@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox