From b59d31c21571995ca717c29eabd4022f35c35169 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Fri, 8 Sep 2006 15:55:53 +0000 Subject: Tweak the behavior of log_duration as proposed by Guillaume Smet: rather than being equivalent to setting log_min_duration_statement to zero, this option now forces logging of all query durations, but doesn't force logging of query text. Also, add duration logging coverage for fastpath function calls. --- doc/src/sgml/config.sgml | 29 ++++++++++++++--------------- 1 file changed, 14 insertions(+), 15 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index 669110a5fda..2dcde4c14d1 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -1,4 +1,4 @@ - + Server Configuration @@ -2718,23 +2718,22 @@ SELECT * FROM parent WHERE key = 2400; Only superusers can change this setting. - - For clients using extended query protocol, durations of the Parse, - Bind, and Execute steps are logged independently. - + + For clients using extended query protocol, durations of the Parse, + Bind, and Execute steps are logged independently. + - When using this option together with - , - the text of statements that are logged because of - log_statement will not be repeated in the - duration log message. - If you are not using syslog, it is recommended - that you log the PID or session ID using - - so that you can link the statement message to the later - duration message using the process ID or session ID. + The difference between setting this option and setting + to zero is that + exceeding log_min_duration_statement forces the text of + the query to be logged, but this option doesn't. Thus, if + log_duration is on and + log_min_duration_statement has a positive value, all + durations are logged but the query text is included only for + statements exceeding the threshold. This behavior can be useful for + gathering statistics in high-load installations. -- cgit v1.2.3