From: | "Bossart, Nathan" <bossartn(at)amazon(dot)com> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Magnus Hagander <magnus(at)hagander(dot)net>, Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>, Don Seiler <don(at)seiler(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Estimating HugePages Requirements? |
Date: | 2021-09-08 17:48:16 |
Message-ID: | CEF782DE-D929-4D26-A984-7BE119CAC9F6@amazon.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-hackers |
On 9/7/21, 8:50 PM, "Michael Paquier" <michael(at)paquier(dot)xyz> wrote:
> Switched the variable name to shared_memory_size_mb for easier
> grepping, moved it to a more correct location with the other read-only
> GUCS, and applied 0002. Well, 0001 here.
Thanks! And thanks for cleaning up the small mistake in aa37a43.
> + This can be used on a running server for most parameters. However,
> + the server must be shut down for some runtime-computed parameters
> + (e.g., <xref linkend="guc-huge-pages-required"/>).
> Perhaps we should add a couple of extra parameters here, like
> shared_memory_size, and perhaps wal_segment_size? The list does not
> have to be complete, just meaningful enough.
Good idea.
Nathan
From | Date | Subject | |
---|---|---|---|
Next Message | Bossart, Nathan | 2021-09-08 17:52:33 | Re: Estimating HugePages Requirements? |
Previous Message | Prabir Kr Sarkar | 2021-09-08 10:46:50 | Re: Grafana unable to connect Azure Postgresql Flexible server |
From | Date | Subject | |
---|---|---|---|
Next Message | Bossart, Nathan | 2021-09-08 17:52:33 | Re: Estimating HugePages Requirements? |
Previous Message | Peter Geoghegan | 2021-09-08 17:46:14 | Re: The Free Space Map: Problems and Opportunities |