Re: Use case for enabling log_duration other than benchmarking

2023-01-17 Thread Bruce Momjian
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

Re: Use case for enabling log_duration other than benchmarking

2023-01-10 Thread Julien Rouhaud
Le mer. 11 janv. 2023 à 00:28, Ron a écrit : > If your application *requires* subsecond response, and you're only > getting subsecond response some of the time, then you obviously want to > know why. Part of that is checking to see if the database and queries are > doing their job. > now that l

Re: Use case for enabling log_duration other than benchmarking

2023-01-10 Thread Ron
On 1/10/23 09:57, Alicja Kucharczyk wrote: wt., 10 sty 2023 o 14:57 Ron napisał(a): On 1/10/23 07:14, Alicja Kucharczyk wrote: Do you know any use case for enabling log_duration? Like 3rd party tools for instance. I find this parameter pretty much useless (in opposite to lo

Re: Use case for enabling log_duration other than benchmarking

2023-01-10 Thread Alicja Kucharczyk
wt., 10 sty 2023 o 14:57 Ron napisał(a): > On 1/10/23 07:14, Alicja Kucharczyk wrote: > > Do you know any use case for enabling log_duration? Like 3rd party tools > for instance. > I find this parameter pretty much useless (in opposite to > log_min_duration_statement) as it does not show the quer

Re: Use case for enabling log_duration other than benchmarking

2023-01-10 Thread Ron
On 1/10/23 07:14, Alicja Kucharczyk wrote: Do you know any use case for enabling log_duration? Like 3rd party tools for instance. I find this parameter pretty much useless (in opposite to log_min_duration_statement) as it does not show the query text, so besides having just the timing logged it