Re: problems with "Shared Memory and Semaphores" section of docs - Mailing list pgsql-hackers

From Nathan Bossart
Subject Re: problems with "Shared Memory and Semaphores" section of docs
Date
Msg-id 20240517192633.GB1933425@nathanxps13
Whole thread Raw
In response to Re: problems with "Shared Memory and Semaphores" section of docs  ("Imseih (AWS), Sami" <simseih@amazon.com>)
List 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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Add new protocol message to change GUCs for usage with future protocol-only GUCs
Next
From: Andres Freund
Date:
Subject: Re: problems with "Shared Memory and Semaphores" section of docs