| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Seino Yuki <seinoyu(at)oss(dot)nttdata(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Doc: shared_memory_size_in_huge_pages with the "SHOW" command. |
| Date: | 2024-10-16 01:46:44 |
| Message-ID: | CAKFQuwY+59_FofYO-ZeFMa2Dnn8Wq6soU8W3y2u-baDATGcY6w@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Friday, October 11, 2024, Seino Yuki <seinoyu(at)oss(dot)nttdata(dot)com> wrote:
>
>
> The current documentation explains the use of the postgres -C command,
> but this method may be limited in DBaaS or managed service environments.
> In particular, CloudNativePG does not allow the server to be stopped,
> making the execution of $ postgres -C impossible.
If your environment doesn’t allow shutting down the Postgres service it
seems highly unlikely you’d be able to perform the other low-level
operating system actions required here as well.
I think the wording is fine as-is, though for consistency with an earlier
mention on the page we could instead write:
This parameter can be viewed before starting the server with a postgres command
like:
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2024-10-16 02:21:44 | Re: Fixing Hash Join bug I caused with adf97c156 |
| Previous Message | Nathan Bossart | 2024-10-16 01:26:06 | Re: Doc: shared_memory_size_in_huge_pages with the "SHOW" command. |