Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.92)
	(envelope-from <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1j9rjC-0000Ae-DK
	for pgsql-admin@arkaria.postgresql.org; Thu, 05 Mar 2020 14:43:58 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.89)
	(envelope-from <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1j9rjB-0000Ue-36
	for pgsql-admin@arkaria.postgresql.org; Thu, 05 Mar 2020 14:43:57 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <scott_ribe@elevated-dev.com>)
	id 1j9rjA-0000UW-Pu
	for pgsql-admin@lists.postgresql.org; Thu, 05 Mar 2020 14:43:56 +0000
Received: from mailout.easymail.ca ([64.68.200.34])
	by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <scott_ribe@elevated-dev.com>)
	id 1j9rj7-0000tC-Fv
	for pgsql-admin@postgresql.org; Thu, 05 Mar 2020 14:43:56 +0000
Received: from localhost (localhost [127.0.0.1])
	by mailout.easymail.ca (Postfix) with ESMTP id 34396BFF3E
	for <pgsql-admin@postgresql.org>; Thu,  5 Mar 2020 14:43:51 +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 mI6Ngsv7kLPc for <pgsql-admin@postgresql.org>;
	Thu,  5 Mar 2020 14:43:51 +0000 (UTC)
Received: from [192.168.2.127] (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 C8680BFF10
	for <pgsql-admin@postgresql.org>; Thu,  5 Mar 2020 14:43:50 +0000 (UTC)
From: Scott Ribe <scott_ribe@elevated-dev.com>
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.60.0.2.5\))
Subject: shm
Message-Id: <565DBAD4-E79D-4EE0-89C4-ABE33AD0C0A7@elevated-dev.com>
Date: Thu, 5 Mar 2020 07:43:49 -0700
To: pgsql-admin <pgsql-admin@postgresql.org>
X-Mailer: Apple Mail (2.3608.60.0.2.5)
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

What is POSIX shared memory used for anymore? Shared buffers now =
defaults to mmap, right? So when I run out of shm in Kubernetes because =
of the 64MB limit, what is actually causing it to run out?

(I know about creating the memory-based volume and mounting it at =
/dev/shm, and have implemented that workaround. Still want to know what =
is causing this memory use.)

--
Scott Ribe
scott_ribe@elevated-dev.com
https://www.linkedin.com/in/scottribe/