Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1krizu-0000lk-Lu
	for pgsql-admin@arkaria.postgresql.org; Tue, 22 Dec 2020 14:50:46 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1krizs-0007si-OY
	for pgsql-admin@arkaria.postgresql.org; Tue, 22 Dec 2020 14:50:44 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <scott_ribe@elevated-dev.com>)
	id 1krizs-0007sa-HH
	for pgsql-admin@lists.postgresql.org; Tue, 22 Dec 2020 14:50:44 +0000
Received: from mailout.easymail.ca ([64.68.200.34])
	by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <scott_ribe@elevated-dev.com>)
	id 1krizq-0003NQ-8Z
	for pgsql-admin@lists.postgresql.org; Tue, 22 Dec 2020 14:50:43 +0000
Received: from localhost (localhost [127.0.0.1])
	by mailout.easymail.ca (Postfix) with ESMTP id A1B5FC2C80;
	Tue, 22 Dec 2020 14:50:40 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at emo04-pco.easydns.vpn
Received: from mailout.easymail.ca ([127.0.0.1])
	by localhost (emo04-pco.easydns.vpn [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 6HnZS0axGccN; Tue, 22 Dec 2020 14:50:40 +0000 (UTC)
Received: from shr-macbook-pro.local (unknown [4.28.96.150])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by mailout.easymail.ca (Postfix) with ESMTPSA id 86C61C0A1B;
	Tue, 22 Dec 2020 14:50:37 +0000 (UTC)
Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Subject: Re: Memory Issues.
From: Scott Ribe <scott_ribe@elevated-dev.com>
In-Reply-To: <20201222140955.GB23159@depesz.com>
Date: Tue, 22 Dec 2020 07:50:32 -0700
Cc: Sreejith P <sreejith@lifetrenz.com>,
 "pgsql-admin@lists.postgresql.org" <pgsql-admin@lists.postgresql.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <338A7603-01EB-40B3-B348-509B7591C9B6@elevated-dev.com>
References: 
 <PS2PR02MB283729A5CCA2EDA94E75E693F3DF0@PS2PR02MB2837.apcprd02.prod.outlook.com>
 <20201222140955.GB23159@depesz.com>
To: hubert depesz lubaczewski <depesz@depesz.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
List-Id: <pgsql-admin.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-admin@lists.postgresql.org>
List-Owner: <mailto:pgsql-admin-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-admin>
Precedence: bulk

> On Dec 22, 2020, at 7:09 AM, hubert depesz lubaczewski =
<depesz@depesz.com> wrote:
>=20
> 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...