Re: Inconsistency in extended-query-protocol logging - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Inconsistency in extended-query-protocol logging
Date
Msg-id 11389.1158157827@sss.pgh.pa.us
Whole thread Raw
In response to Inconsistency in extended-query-protocol logging  ("Guillaume Smet" <guillaume.smet@gmail.com>)
Responses Re: Inconsistency in extended-query-protocol logging  ("Guillaume Smet" <guillaume.smet@gmail.com>)
List pgsql-hackers
"Guillaume Smet" <guillaume.smet@gmail.com> writes:
> I attached a patch to improve the consistency. It adds statement: for
> every case.

Isn't that just bloating the log?  And weren't you the one complaining
about log volumes to begin with?

The reason it is why it is is that Bruce wanted the wording to reflect
why you are getting the log message: anything starting "statement:"
is being logged because of log_statement, anything starting "duration:"
is being logged because of one of the log_duration variables.  Your
proposed patch blurs that distinction and doesn't buy anything much
that I can see.
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Andrew Dunstan"
Date:
Subject: Re: Getting a move on for 8.2 beta
Next
From: Tom Lane
Date:
Subject: Re: -HEAD planner issue wrt hash_joins on dbt3 ?