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

From John Scalia
Subject Re: Understanding was terminated by signal 9: Killed
Date
Msg-id AEEF347B-39EC-41FC-8AC9-2AFA54F71391@gmail.com
Whole thread Raw
In response to Re: Understanding was terminated by signal 9: Killed  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses RE: Understanding was terminated by signal 9: Killed  ("Michel SALAIS" <msalais@msym.fr>)
List pgsql-admin
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
>
>



pgsql-admin by date:

Previous
From: Tom Lane
Date:
Subject: Re: Understanding was terminated by signal 9: Killed
Next
From: Mladen Gogala
Date:
Subject: Re: Renaming 800GB size table in postgresql