Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtp (Exim 4.84_2)
	(envelope-from <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1ebweO-0006d1-MI
	for pgsql-admin@arkaria.postgresql.org; Wed, 17 Jan 2018 22:57:44 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.84_2)
	(envelope-from <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1ebweN-0006Hn-NZ
	for pgsql-admin@arkaria.postgresql.org; Wed, 17 Jan 2018 22:57:43 +0000
Received: from makus.postgresql.org ([2001:4800:1501:1::229])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.84_2)
	(envelope-from <scott_ribe@elevated-dev.com>)
	id 1ebweN-0006He-DD
	for pgsql-admin@lists.postgresql.org; Wed, 17 Jan 2018 22:57:43 +0000
Received: from mailout.easymail.ca ([64.68.200.34])
	by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from <scott_ribe@elevated-dev.com>)
	id 1ebweK-0002J5-5s
	for pgsql-admin@lists.postgresql.org; Wed, 17 Jan 2018 22:57:41 +0000
Received: from localhost (localhost [127.0.0.1])
	by mailout.easymail.ca (Postfix) with ESMTP id 9061CC0517;
	Wed, 17 Jan 2018 22:57:37 +0000 (UTC)
Received: from mailout.easymail.ca ([127.0.0.1])
	by localhost (emo01-pco.easydns.vpn [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id jvHrVh4YVjz9; Wed, 17 Jan 2018 22:57:37 +0000 (UTC)
Received: from shr-mbp-2.local (unknown [8.39.228.117])
	(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 8FC73C04FC;
	Wed, 17 Jan 2018 22:57:34 +0000 (UTC)
Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
Subject: Re: Abnormally high memory usage/OOM triggered
From: scott ribe <scott_ribe@elevated-dev.com>
In-Reply-To: <4d52fee7-73ba-16a9-9c27-8ae5107ee6ae@gmail.com>
Date: Wed, 17 Jan 2018 15:57:33 -0700
Cc: pgsql-admin@lists.postgresql.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <5E0AB8DB-F13B-41BF-843A-FE64FBE9C097@elevated-dev.com>
References: <4d52fee7-73ba-16a9-9c27-8ae5107ee6ae@gmail.com>
To: Davlet Panech <dpanech@gmail.com>
X-Mailer: Apple Mail (2.3445.5.20)
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 Jan 17, 2018, at 2:57 PM, Davlet Panech <dpanech@gmail.com> wrote:
>=20
> Does my configuration look reasonable? I just don't understand how it =
could possibly use up 19 GB of memory based on the configuration below. =
Is there a memory leak in there somewhere?

It does seem awfully high, but... An update can involve a join across =
multiple tables. Or an update can run a trigger which can cascade. =
Either of those could result in an "accidental cross product" join, =
which can always blow up memory.

--
Scott Ribe
https://www.linkedin.com/in/scottribe/
(303) 722-0567