| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | "Sisson, David" <David(dot)Sisson(at)dell(dot)com> |
| Cc: | Christophe Pettus <xof(at)thebuild(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <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-23 20:00:45 |
| Message-ID: | CAKFQuwZD+iVWJ4-hko+CzOx3JMK8E87cwYbqPcGiOr9stau+qw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, Jan 23, 2023 at 12:51 PM Sisson, David <David(dot)Sisson(at)dell(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sisson, David | 2023-01-23 20:12:18 | RE: BUG #17757: Not honoring huge_pages setting during initdb causes DB crash in Kubernetes |
| Previous Message | Tom Lane | 2023-01-23 19:55:50 | Re: BUG #17757: Not honoring huge_pages setting during initdb causes DB crash in Kubernetes |