From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> |
Cc: | david_sisson(at)dell(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #17757: Not honoring huge_pages setting during initdb causes DB crash in Kubernetes |
Date: | 2023-01-22 01:01:08 |
Message-ID: | 1122629.1674349268@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2023-01-22 02:08:26 | Re: BUG #17757: Not honoring huge_pages setting during initdb causes DB crash in Kubernetes |
Previous Message | Tomas Vondra | 2023-01-22 00:55:01 | Re: BUG #17757: Not honoring huge_pages setting during initdb causes DB crash in Kubernetes |