Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 0318e6e

Browse files
author
Commitfest Bot
committed
[CF 4718] Set log_lock_waits=on by default
This branch was automatically generated by a robot using patches from an email thread registered at: https://commitfest.postgresql.org/patch/4718 The branch will be overwritten each time a new patch version is posted to the thread, and also periodically to check for bitrot caused by changes on the master branch. Patch(es): https://www.postgresql.org/message-id/659ffa38.170a0220.eea6a.28fc@mx.google.com Author(s): Laurenz Albe
2 parents fe29b2a + b06ff0f commit 0318e6e

File tree

1 file changed

+6
-5
lines changed

1 file changed

+6
-5
lines changed

doc/src/sgml/config.sgml

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -11132,11 +11132,12 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir'
1113211132
</para>
1113311133

1113411134
<para>
11135-
When <xref linkend="guc-log-lock-waits"/> is set,
11136-
this parameter also determines the amount of time to wait before
11137-
a log message is issued about the lock wait. If you are trying
11138-
to investigate locking delays you might want to set a shorter than
11139-
normal <varname>deadlock_timeout</varname>.
11135+
When <xref linkend="guc-log-lock-waits"/> is set to
11136+
<literal>on</literal> (which is the default), this parameter also
11137+
determines the amount of time to wait before a log message is issued
11138+
about the lock wait. If you are trying to investigate locking delays
11139+
you might want to set a shorter than normal
11140+
<varname>deadlock_timeout</varname>.
1114011141
</para>
1114111142
</listitem>
1114211143
</varlistentry>

0 commit comments

Comments
 (0)