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

From David G. Johnston
Subject Re: BUG #17757: Not honoring huge_pages setting during initdb causes DB crash in Kubernetes
Date
Msg-id CAKFQuwZD+iVWJ4-hko+CzOx3JMK8E87cwYbqPcGiOr9stau+qw@mail.gmail.com
Whole thread Raw
In response to RE: BUG #17757: Not honoring huge_pages setting during initdb causes DB crash in Kubernetes  ("Sisson, David" <David.Sisson@dell.com>)
List pgsql-bugs
On Mon, Jan 23, 2023 at 12:51 PM Sisson, David <David.Sisson@dell.com> wrote:
The default is "huge_pages = try" which is commented out in the "postgresql.conf.sample" file.
When a consumer like myself turns it off in the standard "postgresql.conf" file, it should not be turned on when initdb runs.
There is no way to turn it off without altering the sample config file.


Right, the present way to control what is seen by initdb is postgresql.conf.sample since that is the template that initdb uses to then produce an actual postgresql.conf for the newly created instance.  postgresql.conf is only ever a per-instance configuration file.  It doesn't make sense to "change postgresql.conf in hopes of influencing some future initdb run."

David J.

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: "Sisson, David"
Date:
Subject: RE: BUG #17757: Not honoring huge_pages setting during initdb causes DB crash in Kubernetes