| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Seino Yuki <seinoyu(at)oss(dot)nttdata(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Doc: shared_memory_size_in_huge_pages with the "SHOW" command. |
| Date: | 2024-10-16 01:26:06 |
| Message-ID: | Zw8WLvyjsbz64NOD@nathan |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Oct 16, 2024 at 09:31:49AM +0900, Michael Paquier wrote:
> I am not sure that neither mentioning nor recommending SHOW for this
> area is a good idea, the point being to encourage its use before the
> server is running as we don't want to allocate anything when tuning
> it.
Agreed.
> Point taken that the current wording can be confusing because of the
> "*must* be shut down". How about doing a simpler s/must/should/ for a
> softer wording?
Well, the point is that you can't use "postgres -C" to view this GUC while
the server is running. I can see how the present wording might be
misinterpreted, though. Perhaps we should change this sentence to
something like:
Note that the server must be shut down to view this runtime-computed
parameter with the postgres command.
--
nathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2024-10-16 01:46:44 | Re: Doc: shared_memory_size_in_huge_pages with the "SHOW" command. |
| Previous Message | Michael Paquier | 2024-10-16 01:24:32 | Re: Large expressions in indexes can't be stored (non-TOASTable) |