| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Sisson, David" <David(dot)Sisson(at)dell(dot)com>, 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-24 00:37:37 |
| Message-ID: | 20230124003737.owezrb6ffen6dhb3@awork3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hi,
On 2023-01-23 17:51:46 -0500, Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2023-01-24 00:45:19 | Re: BUG #17757: Not honoring huge_pages setting during initdb causes DB crash in Kubernetes |
| Previous Message | Tom Lane | 2023-01-23 22:51:46 | Re: BUG #17757: Not honoring huge_pages setting during initdb causes DB crash in Kubernetes |