| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | "Imseih (AWS), Sami" <simseih(at)amazon(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: problems with "Shared Memory and Semaphores" section of docs |
| Date: | 2024-05-17 19:26:33 |
| Message-ID: | 20240517192633.GB1933425@nathanxps13 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, May 17, 2024 at 06:30:08PM +0000, Imseih (AWS), Sami wrote:
>> The advantage of the GUC is that its value could be seen before trying to
>> actually start the server.
>
> Only if they have a sample in postgresql.conf file, right?
> A GUC like shared_memory_size_in_huge_pages will not be.
shared_memory_size_in_huge_pages is computed at runtime and can be viewed
with "postgres -C" before actually trying to start the server [0].
[0] https://www.postgresql.org/docs/devel/kernel-resources.html#LINUX-HUGE-PAGES
--
Nathan Bossart
Amazon Web Services: https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2024-05-17 19:28:20 | Re: problems with "Shared Memory and Semaphores" section of docs |
| Previous Message | Robert Haas | 2024-05-17 19:24:26 | Re: Add new protocol message to change GUCs for usage with future protocol-only GUCs |