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 1pJNJi-0004GB-8f for pgsql-bugs@arkaria.postgresql.org; Sat, 21 Jan 2023 23:30:34 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pJNJh-0006Hg-5N for pgsql-bugs@arkaria.postgresql.org; Sat, 21 Jan 2023 23:30:33 +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 1pJNJg-0006Fz-TW for pgsql-bugs@lists.postgresql.org; Sat, 21 Jan 2023 23:30:32 +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 1pJNJe-0006g3-U7 for pgsql-bugs@lists.postgresql.org; Sat, 21 Jan 2023 23:30:32 +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 30LNURZZ1113116; Sat, 21 Jan 2023 18:30:27 -0500 From: Tom Lane To: Tomas Vondra cc: david_sisson@dell.com, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #17757: Not honoring huge_pages setting during initdb causes DB crash in Kubernetes In-reply-to: <4ce40288-5b88-f9fb-ea11-fc932c61472b@enterprisedb.com> References: <17757-dbdfc1f1c954a6db@postgresql.org> <4ce40288-5b88-f9fb-ea11-fc932c61472b@enterprisedb.com> Comments: In-reply-to Tomas Vondra message dated "Sun, 22 Jan 2023 00:10:29 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1113114.1674343827.1@sss.pgh.pa.us> Date: Sat, 21 Jan 2023 18:30:27 -0500 Message-ID: <1113115.1674343827@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Tomas Vondra writes: > On 1/20/23 23:48, PG Bug reporting form wrote: >> Here is a PR with a possible fix: >> https://github.com/postgres/postgres/pull/114/files > I doubt we want to just go straight to changing the default value for > everyone. Yeah, that proposal is a non-starter. I could see providing an initdb option to adjust the value applied during initdb, though. Ideally, maybe what we want is a generalized switch that could replace any variable in the sample config, along the lines of the server's "-c foo=bar". I recall having tried to do that and having run into quoting hazards, but I did not try very hard. regards, tom lane