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: Wed, 20 Oct 2021 16:39:04 -0400
Message-Id: <B824B1DB-5868-4982-BA8B-FF607CE0EA39@gmail.com>
References: <006701d7c5f0$e4ddc100$ae994300$@msym.fr>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Wells Oliver <wells.oliver@gmail.com>,
 pgsql-admin <pgsql-admin@postgresql.org>
In-Reply-To: <006701d7c5f0$e4ddc100$ae994300$@msym.fr>
To: Michel SALAIS <msalais@msym.fr>
Archived-At: 
 <https://www.postgresql.org/message-id/B824B1DB-5868-4982-BA8B-FF607CE0EA39%40gmail.com>
Precedence: bulk

That would be news to me. Where I currently work we=E2=80=99ve had to do tha=
t on several occasions as many of our dbs are in the multi- multi- terabyte r=
ange, 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:
>=20
> =EF=BB=BFBe careful!
> I am not sure but upgrade for a larger instance can't be temporary. I thin=
k you can't downgrade to the original instance  class thereafter...
>=20
> --
> Michel SALAIS
>=20
> -----Message d'origine-----
> De : John Scalia <jayknowsunix@gmail.com>=20
> Envoy=C3=A9 : mercredi 20 octobre 2021 01:12
> =C3=80 : Tom Lane <tgl@sss.pgh.pa.us>
> Cc : Wells Oliver <wells.oliver@gmail.com>; pgsql-admin <pgsql-admin@postg=
resql.org>
> Objet : Re: Understanding was terminated by signal 9: Killed
>=20
> You could always change the size of the RDS instance to something larger t=
han what it currently is running, even just temporarily.
>=20
> Sent from my iPad
>=20
>> 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=20=

>>> setting temp_buffers to 16GB, so I think I plum ran out of memory,=20
>>> but can anyone point me in a different direction if the following log=20=

>>> messages indicate something else is awry?
>>=20
>> Yeah, this:
>>=20
>>> 2021-10-19 21:10:37 UTC::@:[24752]:LOG:  server process (PID 25813)=20
>>> was terminated by signal 9: Killed
>>=20
>> almost certainly indicates the Linux OOM killer at work.  If you were=20
>> running your own system I'd point you to [1], but I doubt that RDS=20
>> lets you put your hands on the relevant knobs.
>>=20
>>           regards, tom lane
>>=20
>> [1]=20
>> https://www.postgresql.org/docs/current/kernel-resources.html#LINUX-ME
>> MORY-OVERCOMMIT
>>=20
>>=20
>=20
>=20