From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Christian Robottom Reis <kiko(at)async(dot)com(dot)br>, pgsql-docs(at)postgresql(dot)org, Guilherme Salgado <salgado(at)async(dot)com(dot)br> |
Subject: | Re: log_min_duration_statement versus log_statement |
Date: | 2005-06-29 21:32:55 |
Message-ID: | 200506291432.56196.josh@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2005-07-01 13:24:47 | Problem with on/off, true/false in postgresql.conf |
Previous Message | Christian Robottom Reis | 2005-06-29 19:40:20 | Re: log_min_duration_statement versus log_statement |