RE: libpq debug log - Mailing list pgsql-hackers

From tsunakawa.takay@fujitsu.com
Subject RE: libpq debug log
Date
Msg-id TYAPR01MB2990FA689A57272C96948207FEB39@TYAPR01MB2990.jpnprd01.prod.outlook.com
Whole thread Raw
In response to Re: libpq debug log  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-hackers
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
> I'm pretty sure I named the flag PQTRACE_SUPPRESS_TIMESTAMP (and I
> prefer SUPPRESS to NOOUTPUT), because the idea is that the timestamp is
> printed by default.  I think that's the sensible decision: applications
> prefer to have timestamps, even if there's a tiny bit of overhead.  We
> don't want to force them to pass a flag for that.  We only want the
> no-timestamp behavior in order to be able to use it for libpq internal
> testing.

Agreed.  It makes sense to print timestamps by default because this feature will be used to diagnose slowness outside
thedatabase server.  (I misunderstood the motivation to introduce the flag).
 




Regards
Takayuki Tsunakawa



pgsql-hackers by date:

Previous
From: torikoshia
Date:
Subject: Re: Is it useful to record whether plans are generic or custom?
Next
From: Zhihong Yu
Date:
Subject: Re: WIP: BRIN multi-range indexes