Re: BUG #17757: Not honoring huge_pages setting during initdb causes DB crash in Kubernetes

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-21 23:30:27
Message-ID: 1113115.1674343827@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/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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2023-01-21 23:33:03 Re: BUG #17757: Not honoring huge_pages setting during initdb causes DB crash in Kubernetes
Previous Message Andres Freund 2023-01-21 23:29:22 Re: BUG #17757: Not honoring huge_pages setting during initdb causes DB crash in Kubernetes