Re: Set log_lock_waits=on by default

Поиск
Список
Период
Сортировка
От Chao Li
Тема Re: Set log_lock_waits=on by default
Дата
Msg-id 80A10B63-DD7E-4057-A4EB-E2CA3CA1A796@gmail.com
обсуждение исходный текст
Ответ на Re: Set log_lock_waits=on by default  (Laurenz Albe <laurenz.albe@cybertec.at>)
Ответы Re: Set log_lock_waits=on by default
Список pgsql-hackers
Дерево обсуждения


On Sep 8, 2025, at 05:46, Laurenz Albe <laurenz.albe@cybertec.at> wrote:

On Thu, 2025-09-04 at 14:12 +0900, Shinya Kato wrote:
Due to 635998965 [0], you need to change guc_parameters.dat instead of
guc_tables.c.

Thanks for pointing that out to me!
Here is an updated patch.

Yours,
Laurenz Albe
<v2-0001-Default-to-log_lock_waits-on.patch>

I am hesitate to support this change. I agree log_lock_waits is a powerful tool, but it’s more like a diagnostic tool. On a high-concurrency system with many tractions running at the same time, it may quickly fill up log files and make it difficult to find other errors. So, we usually only turn it on when needed, and turn it off once debugging is done.

But v2 code looks good to me.

Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/




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