Re: Estimating HugePages Requirements?

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: Estimating HugePages Requirements?
Дата
Msg-id YntK4a8ET4dW0E4L@paquier.xyz
обсуждение исходный текст
Ответ на Re: Estimating HugePages Requirements?  (Nathan Bossart <nathandbossart@gmail.com>)
Ответы Re: Estimating HugePages Requirements?  (Nathan Bossart <nathandbossart@gmail.com>)
Список pgsql-hackers
On Tue, May 10, 2022 at 09:12:49AM -0700, Nathan Bossart wrote:
> AFAICT you need to set log_min_messages to at least DEBUG3 to see extra
> output for the non-runtime-computed GUCs, so it might not be worth the
> added complexity.

This set of messages is showing up for ages with zero complaints from
the field AFAIK, and nobody would use this level of logging except
developers.  One thing that overriding log_min_messages to FATAL does,
however, is to not show anymore those debug3 messages when querying a
runtime-computed GUC, but that's the kind of things we'd hide.  Your
patch would hide those entries in both cases.  Perhaps we could do
that, but at the end, I don't really see any need to complicate this
code path more than necessary, and this is enough to silence the logs
in the cases we care about basically all the time, even if the log
levels are reduced a bit on a given cluster.  Hence, I have applied
the simplest solution to just enforce a log_min_messages=FATAL when
requesting a runtime GUC.
--
Michael

Вложения

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

Предыдущее
От: Noah Misch
Дата:
Сообщение: Re: Rewriting the test of pg_upgrade as a TAP test - take three - remastered set
Следующее
От: Michael Paquier
Дата:
Сообщение: Re: Allowing REINDEX to have an optional name