| From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Cc: | min(dot)xx(dot)zhang(at)ericsson(dot)com |
| Subject: | BUG #17323: test_config_settings during postgres initialization does not read the parameter huge_pages |
| Date: | 2021-12-06 15:07:41 |
| Message-ID: | 17323-3062535b45e1cfc2@postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 17323
Logged by: min zhang
Email address: min(dot)xx(dot)zhang(at)ericsson(dot)com
PostgreSQL version: 10.18
Operating system: SUSE linux
Description:
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.
In a K8s cluster environment, sometimes this will lead to the testing
process core dump.
So we write this bug report to make the testing process read the parameter
huge_pages to avoid core dump.
Thanks.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-12-06 15:42:48 | Re: BUG #17323: test_config_settings during postgres initialization does not read the parameter huge_pages |
| Previous Message | Tom Lane | 2021-12-06 14:56:40 | Re: BUG #17318: ERROR: AddressSanitizer: SEGV on unknown address in optimizer |