From: Tomas Vondra <tomas.vondra@enterprisedb.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: david_sisson@dell.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17757: Not honoring huge_pages setting during initdb causes DB crash in Kubernetes
Date: Sun, 22 Jan 2023 01:55:01 +0100
Message-ID: <127328f2-4e01-e9ec-c9b1-76aef967343f@enterprisedb.com> (raw)
In-Reply-To: <1113115.1674343827@sss.pgh.pa.us>
References: <17757-dbdfc1f1c954a6db@postgresql.org>
<4ce40288-5b88-f9fb-ea11-fc932c61472b@enterprisedb.com>
<1113115.1674343827@sss.pgh.pa.us>
On 1/22/23 00:30, Tom Lane wrote:
> Tomas Vondra <tomas.vondra@enterprisedb.com> 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.
>
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 ...
regards
--
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tomas.vondra@enterprisedb.com, tgl@sss.pgh.pa.us, 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>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox