Re: BUG #17757: Not honoring huge_pages setting during initdb causes DB crash in Kubernetes - Mailing list pgsql-bugs

From Andres Freund
Subject Re: BUG #17757: Not honoring huge_pages setting during initdb causes DB crash in Kubernetes
Date
Msg-id 20230124003737.owezrb6ffen6dhb3@awork3.anarazel.de
Whole thread Raw
In response to Re: BUG #17757: Not honoring huge_pages setting during initdb causes DB crash in Kubernetes  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #17757: Not honoring huge_pages setting during initdb causes DB crash in Kubernetes  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Hi,

On 2023-01-23 17:51:46 -0500, Tom Lane wrote:
> Andres Freund <andres@anarazel.de> writes:
> > That said, I'm for allowing to specify options to initdb.
> 
> Yeah, I think that has enough other potential applications to be worth
> doing.  Here's a quick draft patch (sans user-facing docs as yet).
> It injects any given values into postgresql.auto.conf, not
> postgresql.conf proper.  I did that mainly because the latter looked
> beyond the abilities of the primitive string-munging code we have in
> there, but I think it can be argued to be a reasonable choice anyway.

Oh, I had thought we'd just pass them on with -c to the processes that initdb
starts. But perhaps just persisting them isn't a bad idea...

- Andres



pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #17757: Not honoring huge_pages setting during initdb causes DB crash in Kubernetes
Next
From: Tom Lane
Date:
Subject: Re: BUG #17757: Not honoring huge_pages setting during initdb causes DB crash in Kubernetes