From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: david_sisson@dell.com
Subject: BUG #17757: Not honoring huge_pages setting during initdb causes DB crash in Kubernetes
Date: Fri, 20 Jan 2023 22:48:09 +0000
Message-ID: <17757-dbdfc1f1c954a6db@postgresql.org> (raw)
The following bug has been logged on the website:
Bug reference: 17757
Logged by: David Angel
Email address: david_sisson@dell.com
PostgreSQL version: 14.5
Operating system: Linux
Description:
On an OS where hugepages are enabled, if no hugepages resources are assigned
in Kubernetes and the postgres instance is set to hugepages = off in the
config then one would assume that the DB would not use hugepages.
However, because the initdb process uses postgresql.conf.sample or
postgresql.conf.template instead of the actual specified configuration the
applied setting is actually hugepages = try during initdb.
In these cases, the initdb phase will attempt to allocate huge pages that
are available in the OS, but it will be denied access by Kubernetes and
fail.
Here is a PR with a possible fix:
https://github.com/postgres/postgres/pull/114/files
Here are some links for further information
Ours: https://github.com/CrunchyData/postgres-operator/issues/3477
Others with the same having no solution to disable huge pages.
https://github.com/CrunchyData/postgres-operator/issues/3039https://github.com/CrunchyData/postgres-operator/issues/2258https://github.com/CrunchyData/postgres-operator/issues/3126https://github.com/CrunchyData/postgres-operator/issues/3421
Bitnami
https://github.com/bitnami/charts/issues/7901
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, david_sisson@dell.com
Subject: Re: BUG #17757: Not honoring huge_pages setting during initdb causes DB crash in Kubernetes
In-Reply-To: <17757-dbdfc1f1c954a6db@postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox