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
In-reply-to: <17323-3062535b45e1cfc2@postgresql.org>
References: <17323-3062535b45e1cfc2@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Mon, 06 Dec 2021 15:07:41 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3050764.1638805368.1@sss.pgh.pa.us>
Date: Mon, 06 Dec 2021 10:42:48 -0500
Message-ID: <3050765.1638805368@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/3050765.1638805368%40sss.pgh.pa.us>
Precedence: bulk

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