pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: John Scalia <jayknowsunix@gmail.com>
To: Michel SALAIS <msalais@msym.fr>
Cc: 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: Wed, 20 Oct 2021 16:39:04 -0400
Message-ID: <B824B1DB-5868-4982-BA8B-FF607CE0EA39@gmail.com> (raw)
In-Reply-To: <006701d7c5f0$e4ddc100$ae994300$@msym.fr>
References: <006701d7c5f0$e4ddc100$ae994300$@msym.fr>

That would be news to me. Where I currently work we’ve had to do that on several occasions as many of our dbs are in the multi- multi- terabyte range, but some are just references without a lot of traffic.

Sent from my iPad

> On Oct 20, 2021, at 4:27 PM, Michel SALAIS <msalais@msym.fr> wrote:
> 
> Be careful!
> I am not sure but upgrade for a larger instance can't be temporary. I think you can't downgrade to the original instance  class thereafter...
> 
> --
> Michel SALAIS
> 
> -----Message d'origine-----
> De : John Scalia <jayknowsunix@gmail.com> 
> Envoyé : mercredi 20 octobre 2021 01:12
> À : Tom Lane <tgl@sss.pgh.pa.us>
> Cc : Wells Oliver <wells.oliver@gmail.com>; pgsql-admin <pgsql-admin@postgresql.org>
> Objet : Re: Understanding was terminated by signal 9: Killed
> 
> 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-ME
>> MORY-OVERCOMMIT
>> 
>> 
> 
> 





view thread (9+ messages)  latest in thread

Message-ID: <B824B1DB-5868-4982-BA8B-FF607CE0EA39@gmail.com>
Permalink:  ../B824B1DB-5868-4982-BA8B-FF607CE0EA39@gmail.com/
Also on:    postgresql.org/message-id/B824B1DB-5868-4982-BA8B-FF607CE0EA39@gmail.com

 · 

reply

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, msalais@msym.fr, tgl@sss.pgh.pa.us, wells.oliver@gmail.com
  Subject: Re: Understanding was terminated by signal 9: Killed
  In-Reply-To: <B824B1DB-5868-4982-BA8B-FF607CE0EA39@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