| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | "Imseih (AWS), Sami" <simseih(at)amazon(dot)com> |
| Cc: | Nathan Bossart <nathandbossart(at)gmail(dot)com>, 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:28:20 |
| Message-ID: | 20240517192820.vwom64qal36yxxrl@awork3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2024-05-17 18:30:08 +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.
You can query gucs with -C. E.g.
postgres -D pgdev-dev -c shared_buffers=16MB -C shared_memory_size_in_huge_pages
13
postgres -D pgdev-dev -c shared_buffers=16MB -c huge_page_size=1GB -C shared_memory_size_in_huge_pages
1
Which is very useful to be able to actually configure that number of huge
pages. I don't think a system view or such would not help here.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Imseih (AWS), Sami | 2024-05-17 19:34:06 | Re: problems with "Shared Memory and Semaphores" section of docs |
| Previous Message | Nathan Bossart | 2024-05-17 19:26:33 | Re: problems with "Shared Memory and Semaphores" section of docs |