Re: [HACKERS] [PATCHES] log_statement output for protocol - Mailing list pgsql-jdbc

From Tom Lane
Subject Re: [HACKERS] [PATCHES] log_statement output for protocol
Date
Msg-id 28967.1154795245@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] [PATCHES] log_statement output for protocol  (Oliver Jowett <oliver@opencloud.com>)
Responses Re: [HACKERS] [PATCHES] log_statement output for protocol  (Bruce Momjian <bruce@momjian.us>)
List pgsql-jdbc
Oliver Jowett <oliver@opencloud.com> writes:
> A 50-parameter query could be .. interesting ..

> I realize that you need this level of output to reflect what is
> happening at the protocol level, but seeing all the protocol detail is
> not really what you expect when you turn on basic statement logging, is it?

Well, we've certainly been beat up often enough about the lack of
logging bind parameter values --- I don't think there's any question
about the importance of printing them.  I agree that the proposed format
is much too verbose though.  In particular, a separate LOG message per
parameter is NOT what I had in mind; I want them in DETAIL lines of the
bind log message.  (This'd perhaps also address Oliver's issue, since
if you didn't want to see the values you could turn down
log_error_verbosity.)

            regards, tom lane

pgsql-jdbc by date:

Previous
From: David Fetter
Date:
Subject: Re: [HACKERS] [PATCHES] log_statement output for protocol
Next
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] [PATCHES] log_statement output for protocol