From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tomas Vondra <tomas.vondra@enterprisedb.com>
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: <127328f2-4e01-e9ec-c9b1-76aef967343f@enterprisedb.com>
References: <17757-dbdfc1f1c954a6db@postgresql.org>
 <4ce40288-5b88-f9fb-ea11-fc932c61472b@enterprisedb.com>
 <1113115.1674343827@sss.pgh.pa.us>
 <127328f2-4e01-e9ec-c9b1-76aef967343f@enterprisedb.com>
Comments: In-reply-to Tomas Vondra <tomas.vondra@enterprisedb.com>
	message dated "Sun, 22 Jan 2023 01:55:01 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1122628.1674349268.1@sss.pgh.pa.us>
Date: Sat, 21 Jan 2023 20:01:08 -0500
Message-ID: <1122629.1674349268@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1122629.1674349268%40sss.pgh.pa.us>
Precedence: bulk

Tomas Vondra <tomas.vondra@enterprisedb.com> writes:
> On 1/22/23 00:30, Tom Lane wrote:
>> 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.

> Yeah, I was looking for something like "-c" in initdb, only to realize
> there's nothing like that. The main "problem" with adding that is that
> we're unlikely to backpatch that (I guess), and thus it does not really
> solve the issue for the OP.

> I'm not sure we'd be keen to backpatch a change of the default, but
> maybe we would ...

Back-patching a change of default seems like REALLY a non-starter.
Perhaps adding a switch (which would break nothing if not used)
could be discussed, though.

			regards, tom lane