1
0
mirror of https://github.com/postgres/postgres.git synced 2025-05-21 15:54:08 +03:00

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: ivaylo.zlatanov@gmail.com

Discussion: https://postgr.es/m/157019615723.25307.15449102262106437404@wrigleys.postgresql.org

Backpatch-through: 9.4
This commit is contained in:
Bruce Momjian 2019-10-07 14:33:31 -04:00
parent 1b5c2ddcde
commit 7eefec61c9

View File

@ -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 each lock acquisition attempt. The limit applies both to explicit
locking requests (such as <command>LOCK TABLE</>, or <command>SELECT locking requests (such as <command>LOCK TABLE</>, or <command>SELECT
FOR UPDATE</> without <literal>NOWAIT</>) and to implicitly-acquired FOR UPDATE</> without <literal>NOWAIT</>) and to implicitly-acquired
locks. If <varname>log_min_error_statement</> is set to locks. A value of zero (the default) turns this off.
<literal>ERROR</> or lower, the statement that timed out will be
logged. A value of zero (the default) turns this off.
</para> </para>
<para> <para>
@ -6559,7 +6557,9 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv;
while waiting for locks. Note that if <varname>statement_timeout</> while waiting for locks. Note that if <varname>statement_timeout</>
is nonzero, it is rather pointless to set <varname>lock_timeout</> to is nonzero, it is rather pointless to set <varname>lock_timeout</> to
the same or larger value, since the statement timeout would always the same or larger value, since the statement timeout would always
trigger first. trigger first. If <varname>log_min_error_statement</> is set to
<literal>ERROR</> or lower, the statement that timed out will be
logged.
</para> </para>
<para> <para>