Re: Improve logging when using Huge Pages

Поиск
Список
Период
Сортировка
От Alvaro Herrera
Тема Re: Improve logging when using Huge Pages
Дата
Msg-id 20230209094013.67varf63bihops33@alvherre.pgsql
обсуждение исходный текст
Ответ на Re: Improve logging when using Huge Pages  (Justin Pryzby <pryzby@telsasoft.com>)
Ответы Re: Improve logging when using Huge Pages  (Nathan Bossart <nathandbossart@gmail.com>)
Список pgsql-hackers
On 2023-Feb-08, Justin Pryzby wrote:

> I don't think it makes sense to run postgres -C huge_pages_active,
> however, so I see no issue that that would always returns "false".

Hmm, I would initialize it to return "unknown" rather than "off" — and
make sure it turns "off" at the appropriate time.  Otherwise you're just
moving the confusion elsewhere.

> If need be, maybe the documentation could say "indicates whether huge
> pages are active for the running server".

Dunno, that seems way too subtle.

> Does anybody else want to vote for a function rather than a
> RUNTIME_COMPUTED GUC ?

I don't think I'd like to have SELECT show_block_size() et al, so I'd
rather not go that way.

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/
"¿Qué importan los años?  Lo que realmente importa es comprobar que
a fin de cuentas la mejor edad de la vida es estar vivo"  (Mafalda)



В списке pgsql-hackers по дате отправления:

Предыдущее
От: "Takamichi Osumi (Fujitsu)"
Дата:
Сообщение: RE: Time delayed LR (WAS Re: logical replication restrictions)
Следующее
От: Vik Fearing
Дата:
Сообщение: Re: ANY_VALUE aggregate