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 ) id 1pWRIK-0002ZY-6f for pgsql-admin@arkaria.postgresql.org; Mon, 27 Feb 2023 00:23:08 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pWRII-0006F7-IN for pgsql-admin@arkaria.postgresql.org; Mon, 27 Feb 2023 00:23:06 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pWRII-0006Ey-7b for pgsql-admin@lists.postgresql.org; Mon, 27 Feb 2023 00:23:06 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pWRIC-0001Ws-3I for pgsql-admin@lists.postgresql.org; Mon, 27 Feb 2023 00:23:05 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 31R0Mul6099664; Sun, 26 Feb 2023 19:22:56 -0500 From: Tom Lane To: Chris Hoover cc: Evan Rempel , pgsql-admin@lists.postgresql.org Subject: Re: New PG14 server won't start with >2GB shared_buffers In-reply-to: References: <4b583c4a-022f-f452-c0c8-0a932a6ee411@gmail.com> <4a41387e-516e-0782-6110-89c05a99d020@sqlexec.com> <20230225144930.GS9791@aart.rice.edu> <8b47c295-4b16-1a00-32e4-807103816475@uvic.ca> <1177969.1677342917@sss.pgh.pa.us> Comments: In-reply-to Chris Hoover message dated "Sun, 26 Feb 2023 17:01:13 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <99662.1677457376.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Sun, 26 Feb 2023 19:22:56 -0500 Message-ID: <99663.1677457376@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Chris Hoover writes: > Got a chance to work on this today. Here is what I=E2=80=99m getting. = I used the same command that is used when the config has small memory. OK, so it still happens when interactive, which seems to exclude systemd. Have you tried setting huge_pages =3D off, as somebody suggested upthread? (The default setting of "try" ought to work anyway, but we've heard a few reports suggesting sometimes it doesn't.) Googling for ways to limit resources under Linux led me to mentions of /etc/security/limits.conf, which might be worth checking. The comments in that say it only applies to logins via PAM, which should include your interactive session and I'm not too sure about Patroni. Otherwise I'm kind of running out of ideas :-(. *Something* is clearly interfering with your resource limits, but I don't know what. regards, tom lane