doc: move mention of log_min_error_statement in a better spot

Previously it was mentioned in the lock_timeout docs in a confusing
location.

Reported-by: [email protected]
Discussion: https://postgr.es/m/157019615723.25307.15449102262106437404@wrigleys.postgresql.org

Backpatch-through: 9.4

diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 11dee23c7326eda61b4c9764d5c4a40647c8eb58..6c00ec894d0376d62d78b95cf5103b400c00c2f3 100644 (file)
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -6549,9 +6549,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv;
         each lock acquisition attempt.  The limit applies both to explicit
         locking requests (such as LOCK TABLE, or SELECT
         FOR UPDATE without NOWAIT) and to implicitly-acquired
-        locks.  If log_min_error_statement is set to
-        ERROR or lower, the statement that timed out will be
-        logged.  A value of zero (the default) turns this off.
+        locks.  A value of zero (the default) turns this off.
        
 
        
@@ -6559,7 +6557,9 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv;
         while waiting for locks.  Note that if statement_timeout
         is nonzero, it is rather pointless to set lock_timeout to
         the same or larger value, since the statement timeout would always
-        trigger first.
+        trigger first.  If log_min_error_statement is set to
+        ERROR or lower, the statement that timed out will be
+        logged.