| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Alicja Kucharczyk <zaledwie10minut(at)gmail(dot)com> |
| Cc: | Ron <ronljohnsonjr(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Use case for enabling log_duration other than benchmarking |
| Date: | 2023-01-17 21:26:02 |
| Message-ID: | Y8cSagpVTiNaEicv@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Embrace your flaws. They make you human, rather than perfect,
which you will never be.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2023-01-17 21:38:43 | Re: Are ZFS snapshots unsafe when PGSQL is spreading through multiple zpools? |
| Previous Message | David G. Johnston | 2023-01-17 21:22:22 | Re: Maintaining blank lines in psql output? |