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

From Thomas Munro
Subject Re: Improve logging when using Huge Pages
Date
Msg-id CA+hUKGKRfzOH9gji-W7j=iKDQ50AjtGSsUfybNxeNVk+uy2gcg@mail.gmail.com
Whole thread Raw
In response to Re: Improve logging when using Huge Pages  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Improve logging when using Huge Pages
List pgsql-hackers
On Tue, Nov 8, 2022 at 4:56 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Andres Freund <andres@anarazel.de> writes:
> > On 2022-11-06 14:04:29 +0700, John Naylor wrote:
> >> I think the best thing to do is change huge_pages='on' to log a WARNING and
> >> fallback to regular pages if the mapping fails.
>
> > I am strongly opposed to making 'on' fall back to not using huge pages. That's
> > what 'try' is for.
>
> Agreed --- changing "on" to be exactly like "try" isn't an improvement.
> If you want "try" semantics, choose "try".

Agreed, but how can we make the people who want a log message happy,
without upsetting the people who don't want new log messages?  Hence
my suggestion of a new level.  How about try_verbose?



pgsql-hackers by date:

Previous
From: Laurenz Albe
Date:
Subject: Re: New docs chapter on Transaction Management and related changes
Next
From: Thomas Munro
Date:
Subject: Re: Large Pages and Super Pages for PostgreSQL