Re: Improve logging when using Huge Pages
| От | Tom Lane |
|---|---|
| Тема | Re: Improve logging when using Huge Pages |
| Дата | |
| Msg-id | 848204.1679288949@sss.pgh.pa.us обсуждение |
| Ответ на | Re: Improve logging when using Huge Pages (Michael Paquier <michael@paquier.xyz>) |
| Ответы |
Re: Improve logging when using Huge Pages
|
| Список | pgsql-hackers |
Michael Paquier <michael@paquier.xyz> writes:
> On Tue, Mar 14, 2023 at 02:02:19PM +0900, Kyotaro Horiguchi wrote:
>> I slightly prefer using a function for this, as if GUC is used, it can
>> only return "unknown" for the command "postgres -C
>> huge_page_active". However, apart from this advantage, I prefer using
>> a GUC for this information.
> The main advantage of a read-only GUC over a function is that users
> would not need to start a postmaster to know if huge pages would be
> active or not.
I'm confused here, because Horiguchi-san is saying that that
won't work. I've not checked the code lately, but I think that
"postgres -C var" prints its results before actually attempting
to establish shared memory, so I suspect Horiguchi-san is right.
regards, tom lane
В списке pgsql-hackers по дате отправления: