From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
Cc: | francis picabia <fpicabia(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: How to log 'user time' in postgres logs |
Date: | 2019-08-28 14:28:51 |
Message-ID: | 9124.1567002531@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> writes:
> On 8/28/19 5:36 AM, francis picabia wrote:
>> I had no clue the database was the issue because I
>> had the minimal
>> log_duration = on
>> log_line_prefix = '<%t>'
>> With those settings all queries seen were roughly 1ms
>>
>> I need this log to show the true time it takes to get a result back.
> I'm having a hard time believing autovacuum was involved in this, given
> you say the queries took only 1ms on average.
Also: the time logged by log_duration IS the time it took, so far as the
server can tell.
Perhaps there's monstrous network delays involved, but what I'm suspicious
of is inefficient client-side processing.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Browne | 2019-08-28 16:06:26 | Re: Work hours? |
Previous Message | Adrian Klaver | 2019-08-28 14:07:26 | Re: How to log 'user time' in postgres logs |