From 0549ba82e32410892ef0d644212436551974aa2b Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Thu, 19 Oct 2006 22:55:25 +0000 Subject: [PATCH] Clarify note about interaction of log_statement logging with errors. Remove obsolete note about logging of statements generated by plpgsql function execution ... that doesn't happen anymore. --- doc/src/sgml/config.sgml | 22 +++++++++------------- 1 file changed, 9 insertions(+), 13 deletions(-) diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index 549ca755d7..ea6c4efb2a 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -1,4 +1,4 @@ - + Server Configuration @@ -2891,18 +2891,14 @@ SELECT * FROM parent WHERE key = 2400; - Statements that generate syntax errors are not logged. Set - log_min_error_statement to error to - log such statements. - - - - When a function is defined in the - PL/pgSQLserver-side language, any queries - executed by the function will only be logged the first time that the - function is invoked in a particular session. This is because - PL/pgSQL keeps a cache of the - query plans produced for the SQL statements in the function. + Statements that contain simple syntax errors are not logged + even by the log_statement = all setting, + because the log message is emitted only after basic parsing has + been done to determine the statement type. In the case of extended + query protocol, this setting likewise does not log statements that + fail before the Execute phase (i.e., during parse analysis or + planning). Set log_min_error_statement to + error to log such statements.