Re: Estimating HugePages Requirements? - Mailing list pgsql-hackers

From Bossart, Nathan
Subject Re: Estimating HugePages Requirements?
Date
Msg-id C45224E1-29C8-414C-A8E6-B718C07ACB94@amazon.com
Whole thread Raw
In response to Re: Estimating HugePages Requirements?  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On 9/15/21, 7:42 PM, "Michael Paquier" <michael@paquier.xyz> wrote:
> Fixed that, and applied.  Could you rebase the last patch with the
> name suggested for the last GUC, including the docs?  It looks like we
> are heading for shared_memory_size_in_huge_pages.

Thanks!  And done.

For the huge pages setup documentation, I considered sending stderr to
/dev/null to eliminate the LOG from the output, but I opted against
that.  That would've looked like this:

        postgres -D $PGDATA -C shared_memory_size_in_huge_pages 2> /dev/null

Otherwise, there aren't any significant changes in this version of the
patch besides the name change.

Nathan


Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: EXPLAIN(VERBOSE) to CTE with SEARCH BREADTH FIRST fails
Next
From: Andreas Joseph Krogh
Date:
Subject: Re: EXPLAIN(VERBOSE) to CTE with SEARCH BREADTH FIRST fails