From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tomas Vondra <tomas.vondra@enterprisedb.com>
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: Sat, 21 Jan 2023 18:30:27 -0500
Message-ID: <1113115.1674343827@sss.pgh.pa.us> (raw)
In-Reply-To: <4ce40288-5b88-f9fb-ea11-fc932c61472b@enterprisedb.com>
References: <17757-dbdfc1f1c954a6db@postgresql.org>
<4ce40288-5b88-f9fb-ea11-fc932c61472b@enterprisedb.com>
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.
regards, tom lane
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: tgl@sss.pgh.pa.us, tomas.vondra@enterprisedb.com, 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: <1113115.1674343827@sss.pgh.pa.us>
* 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