Re: Use case for enabling log_duration other than benchmarking - Mailing list pgsql-general

From Bruce Momjian
Subject Re: Use case for enabling log_duration other than benchmarking
Date
Msg-id Y8cSagpVTiNaEicv@momjian.us
Whole thread Raw
In response to Re: Use case for enabling log_duration other than benchmarking  (Alicja Kucharczyk <zaledwie10minut@gmail.com>)
List pgsql-general
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  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

Embrace your flaws.  They make you human, rather than perfect,
which you will never be.



pgsql-general by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: Maintaining blank lines in psql output?
Next
From: Bruce Momjian
Date:
Subject: Re: Are ZFS snapshots unsafe when PGSQL is spreading through multiple zpools?