Re: BUG #17757: Not honoring huge_pages setting during initdb causes DB crash in Kubernetes
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: "Sisson, David" <David.Sisson@dell.com>
Cc: Tomas Vondra <tomas.vondra@enterprisedb.com>, Tom Lane <tgl@sss.pgh.pa.us>, "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>
Date: 2023-01-23T19:55:04Z
Lists: pgsql-bugs
Hi, On 2023-01-23 19:26:09 +0000, Sisson, David wrote: > I believe something should be done with PostgreSQL because we are configuring huge_pages = off in the standard "postgresql.conf" file. > huge_pages can be turned on through outside manipulation but it can't be > turned off. It's a fault of the environment if mmap(MAP_HUGETLB) causes a SIGBUS. Normally huge_pages = try is harmless, because it'll just fall back. That source of SIGBUSes needs to be fixed regardless of anything else - plenty allocators try to use huge pages for example, so you'll run into problems regardless of postgres' default. That said, I'm for allowing to specify options to initdb. Greetings, Andres Freund