Re: libpq debug log - Mailing list pgsql-hackers

From Robert Haas
Subject Re: libpq debug log
Date
Msg-id CA+Tgmobk5BN+AueB0Pyh13yK4B1_1+M612gT-p9FgEgF5GNSrw@mail.gmail.com
Whole thread Raw
In response to RE: libpq debug log  ("Jamison, Kirk" <k.jamison@jp.fujitsu.com>)
Responses RE: libpq debug log  ("Iwata, Aya" <iwata.aya@jp.fujitsu.com>)
RE: libpq debug log  ("Jamison, Kirk" <k.jamison@jp.fujitsu.com>)
List pgsql-hackers
On Mon, Feb 18, 2019 at 10:06 PM Jamison, Kirk <k.jamison@jp.fujitsu.com> wrote:
> It sounds more logical to me if there is a parameter that switches on/off the logging
> similar to other postgres logs. I suggest trace_log as the parameter name.

I'm not really sure that I like the design of this patch in any way.
But leaving that aside, trace_log seems like a poor choice of name,
because it's got two words telling you what kind of thing we are doing
(tracing, logging) and zero words describing the nature of the thing
being traced or logged (the wire protocol communication with the
client).  A tracing facility for the planner, or the executor, or any
other part of the system would have an equally good claim on the same
name.  That can't be right.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Haribabu Kommi
Date:
Subject: Re: Pluggable Storage - Andres's take
Next
From: Masahiko Sawada
Date:
Subject: Re: Copy function for logical replication slots