Re: log_min_duration_statement versus log_statement - Mailing list pgsql-docs

From Josh Berkus
Subject Re: log_min_duration_statement versus log_statement
Date
Msg-id 200506291432.56196.josh@agliodbs.com
Whole thread Raw
In response to Re: log_min_duration_statement versus log_statement  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: log_min_duration_statement versus log_statement
List pgsql-docs
Bruce,

> OK, what if we change the documentaiton to be:
>
>     log_min_duration_statement = 1000 # Log all statements whose
>                      # execution time exceeds the value, in
>                      # milliseconds.  -1 disables. Zero logs
>                      # all statements and their durations.
>
> I think you are confused because log_min_duration_statement is really
> about _when_ to log (duration > ? ms), and what to log (the statement).

No, I see what Christian is complaining about.   If one sets
log_statement="All", then all statements will be logged regardless of
duration or the setting in log_min_duration_statement.  So it should
actually read:

     log_min_duration_statement = 1000 # Log all statements whose
                      # execution time exceeds the value, in
                      # milliseconds.  -1 disables. This is in addition to
                         # any statements logged according to
log_statement.

I'm with Christian on wanting to change the behavior so that it does what
the comments says it does currently, but I don't think we'll get that done
today.

--Josh

--
--Josh

Josh Berkus
Aglio Database Solutions
San Francisco

pgsql-docs by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: log_min_duration_statement versus log_statement
Next
From: Christian Robottom Reis
Date:
Subject: Re: log_min_duration_statement versus log_statement