| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| 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>, "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 19:55:50 |
| Message-ID: | 1882151.1674503750@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
"Sisson, David" <David(dot)Sisson(at)dell(dot)com> writes:
> 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.
What "standard postgresql.conf file"? There is no such thing until
initdb creates it.
> There is no way to turn it off without altering the sample config file.
Yup, that's exactly why we are having this discussion.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2023-01-23 20:00:45 | Re: BUG #17757: Not honoring huge_pages setting during initdb causes DB crash in Kubernetes |
| Previous Message | Andres Freund | 2023-01-23 19:55:04 | Re: BUG #17757: Not honoring huge_pages setting during initdb causes DB crash in Kubernetes |