Re: Improve logging when using Huge Pages - Mailing list pgsql-hackers

From Nathan Bossart
Subject Re: Improve logging when using Huge Pages
Date
Msg-id 20230208225634.GA601969@nathanxps13
Whole thread Raw
In response to Re: Improve logging when using Huge Pages  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-hackers
On Thu, Feb 02, 2023 at 04:53:37PM +0100, Alvaro Herrera wrote:
> Maybe I misread the code (actually I only read the patch), but -- does
> it set active=true when huge_pages=on?  I think the code only works when
> huge_pages=try.  That might be pretty confusing; I think it should say
> "on" in both cases.

+1

Also, while this is indeed a runtime-computed parameter, it won't be
initialized until after 'postgres -C' has been handled, so 'postgres -C'
will always report it as "off".  However, I'm not sure it makes sense to
check it with 'postgres -C' anyway since you want to know if the current
server is using huge pages.

At the moment, I think I'd vote for a new function instead of a GUC.

-- 
Nathan Bossart
Amazon Web Services: https://aws.amazon.com



pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: Can we do something to help stop users mistakenly using force_parallel_mode?
Next
From: Matthias van de Meent
Date:
Subject: Re: RFC: WAL infrastructure issues, updates and improvements