From: Tom Lane <tgl@sss.pgh.pa.us>
To: min.xx.zhang@ericsson.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17323: test_config_settings during postgres initialization does not read the parameter huge_pages
Date: Mon, 06 Dec 2021 10:42:48 -0500
Message-ID: <3050765.1638805368@sss.pgh.pa.us> (raw)
In-Reply-To: <17323-3062535b45e1cfc2@postgresql.org>
References: <17323-3062535b45e1cfc2@postgresql.org>
PG Bug reporting form <noreply@postgresql.org> writes:
> In the function test_config_settings() which will run during postgres
> initialization, the logic will create a new process to test what default
> parameters(such as max_connections, shared_buffers) can be set.
> However, it seems the new process so called testing process does not take
> the parameter huge_pages(in postgresql.conf.sample) into account.
The initial configuration will never have huge_pages enabled.
If you want that, it's up to you to adjust the settings
afterwards --- and that typically would also involve changing
shared_buffers. (The settings that initdb would choose are
not large enough to justify worrying about huge pages anyway.)
> In a K8s cluster environment, sometimes this will lead to the testing
> process core dump.
This claim is quite detail-free, so I don't see how we are
supposed to respond to it.
regards, tom lane
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: tgl@sss.pgh.pa.us, min.xx.zhang@ericsson.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17323: test_config_settings during postgres initialization does not read the parameter huge_pages
In-Reply-To: <3050765.1638805368@sss.pgh.pa.us>
* 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