Re: Use case for enabling log_duration other than benchmarking
От
Bruce Momjian
Тема
Re: Use case for enabling log_duration other than benchmarking
Дата
Msg-id
Y8cSagpVTiNaEicv@momjian.us
Ответ на
Re: Use case for enabling log_duration other than benchmarking (Alicja Kucharczyk)
Список
Дерево обсуждения
Use case for enabling log_duration other than benchmarking Alicja Kucharczyk <zaledwie10minut@gmail.com>
Re: Use case for enabling log_duration other than benchmarking Ron <ronljohnsonjr@gmail.com>
Re: Use case for enabling log_duration other than benchmarking Alicja Kucharczyk <zaledwie10minut@gmail.com>
Re: Use case for enabling log_duration other than benchmarking Ron <ronljohnsonjr@gmail.com>
Re: Use case for enabling log_duration other than benchmarking Julien Rouhaud <rjuju123@gmail.com>
Re: Use case for enabling log_duration other than benchmarking Bruce Momjian <bruce@momjian.us>
On Tue, Jan 10, 2023 at 04:57:11PM +0100, Alicja Kucharczyk wrote: > thank you Ron. > My question is a bit more practical - Does anyone really find it useful? > What value brings the info that 20% of my query are under 1ms and 10% over 1 > minute - If just checked once and then turned off - I can understand to have > more visibility into the overall characteristics. But let say someone have it > enabled on a production system all the time - what could be the reason for > that? I think the big value is that enabling log_statement and log_duration prints the statement text when it _starts, while enabling only log_min_duration_statement prints the statement and duration when it _ends_. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Embrace your flaws. They make you human, rather than perfect, which you will never be.
В списке pgsql-general по дате отправления
От: Bruce Momjian
Дата: