"Kevin Grittner" <[EMAIL PROTECTED]> writes:
>>> "statement" isn't a great name for the units
>>> that we are actually processing. We're really wanting to do these
>>> things once per client command, or maybe per client query would be
>>> a better name.
>>
>> Right.
> What about "query string"?
>>> On Mon, Mar 20, 2006 at 7:58 pm, in message
<[EMAIL PROTECTED]>, Bruce Momjian
wrote:
> Tom Lane wrote:
>> But not once per statement --- in reality, you get a fairly
arbitrary
>> behavior that will advance in some cases and not others when
dealing
>> with a multi- statement querystring.
>
"Guillaume Smet" <[EMAIL PROTECTED]> writes:
> As explained in the previous thread, we used to play with log_duration
> and log_min_error_statement to have the following behaviour:
> - log every duration so that we can have a global overview of the
> database activity;
> - log statement only for sl
Hi,
This patch is a followup of a discussion on -hackers about the new
behaviour of log_duration in 8.x (
http://archives.postgresql.org/pgsql-hackers/2006-03/msg00687.php ).
As explained in the previous thread, we used to play with log_duration
and log_min_error_statement to have the following b
