From: Scott Ribe <scott_ribe@elevated-dev.com>
To: hubert depesz lubaczewski <depesz@depesz.com>
Cc: Sreejith P <sreejith@lifetrenz.com>
Cc: pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>
Subject: Re: Memory Issues.
Date: Tue, 22 Dec 2020 07:50:32 -0700
Message-ID: <338A7603-01EB-40B3-B348-509B7591C9B6@elevated-dev.com> (raw)
In-Reply-To: <20201222140955.GB23159@depesz.com>
References: <PS2PR02MB283729A5CCA2EDA94E75E693F3DF0@PS2PR02MB2837.apcprd02.prod.outlook.com>
<20201222140955.GB23159@depesz.com>
> On Dec 22, 2020, at 7:09 AM, hubert depesz lubaczewski <depesz@depesz.com> wrote:
>
> Pg can't really do anything about being killed in this way, so you have
> to track down what is issuing this kill signal, and disable it.
For me, a recent case was an extension we were trying out...
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: scott_ribe@elevated-dev.com, depesz@depesz.com, sreejith@lifetrenz.com, pgsql-admin@lists.postgresql.org
Subject: Re: Memory Issues.
In-Reply-To: <338A7603-01EB-40B3-B348-509B7591C9B6@elevated-dev.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