Commit47571ec

committed

doc: move mention of log_min_error_statement in a better spot

Previously it was mentioned in the lock_timeout docs in a confusinglocation.Reported-by: ivaylo.zlatanov@gmail.comDiscussion:https://postgr.es/m/157019615723.25307.15449102262106437404@wrigleys.postgresql.orgBackpatch-through: 9.4

1 parent3887e94 commit47571ecCopy full SHA for 47571ec

File tree

-4

lines changed

-4

lines changed

Lines changed: 4 additions & 4 deletions

Original file line number	Diff line number	Diff line change
`@@ -7617,17 +7617,17 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv;`
`7617`	`7617`	`each lock acquisition attempt. The limit applies both to explicit`
`7618`	`7618`	`locking requests (such as <command>LOCK TABLE</command>, or <command>SELECT`
`7619`	`7619`	`FOR UPDATE</command> without <literal>NOWAIT</literal>) and to implicitly-acquired`
`7620`		`- locks. If <varname>log_min_error_statement</varname> is set to`
`7621`		`- <literal>ERROR</literal> or lower, the statement that timed out will be`
`7622`		`- logged. A value of zero (the default) turns this off.`
	`7620`	`+ locks. A value of zero (the default) turns this off.`
`7623`	`7621`	`</para>`
`7624`	`7622`
`7625`	`7623`	`<para>`
`7626`	`7624`	`Unlike <varname>statement_timeout</varname>, this timeout can only occur`
`7627`	`7625`	`while waiting for locks. Note that if <varname>statement_timeout</varname>`
`7628`	`7626`	`is nonzero, it is rather pointless to set <varname>lock_timeout</varname> to`
`7629`	`7627`	`the same or larger value, since the statement timeout would always`
`7630`		`- trigger first.`
	`7628`	`+ trigger first. If <varname>log_min_error_statement</varname> is set to`
	`7629`	`+ <literal>ERROR</literal> or lower, the statement that timed out will be`
	`7630`	`+ logged.`
`7631`	`7631`	`</para>`
`7632`	`7632`
`7633`	`7633`	`<para>`

Comments

(0)