Re: BUG #17323: test_config_settings during postgres initialization does not read the parameter huge_pages
От | Tom Lane |
---|---|
Тема | Re: BUG #17323: test_config_settings during postgres initialization does not read the parameter huge_pages |
Дата | |
Msg-id | 3050765.1638805368@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | BUG #17323: test_config_settings during postgres initialization does not read the parameter huge_pages (PG Bug reporting form <noreply@postgresql.org>) |
Ответы |
RE: BUG #17323: test_config_settings during postgres initialization does not read the parameter huge_pages
|
Список | pgsql-bugs |
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
В списке pgsql-bugs по дате отправления: