Commit7eefec6

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 parent1b5c2dd commit7eefec6Copy full SHA for 7eefec6

File tree

-4

lines changed

-4

lines changed

Lines changed: 4 additions & 4 deletions

Original file line number	Diff line number	Diff line change
`@@ -6549,17 +6549,17 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv;`
`6549`	`6549`	`each lock acquisition attempt. The limit applies both to explicit`
`6550`	`6550`	`locking requests (such as <command>LOCK TABLE</>, or <command>SELECT`
`6551`	`6551`	`FOR UPDATE</> without <literal>NOWAIT</>) and to implicitly-acquired`
`6552`		`- locks. If <varname>log_min_error_statement</> is set to`
`6553`		`- <literal>ERROR</> or lower, the statement that timed out will be`
`6554`		`- logged. A value of zero (the default) turns this off.`
	`6552`	`+ locks. A value of zero (the default) turns this off.`
`6555`	`6553`	`</para>`
`6556`	`6554`
`6557`	`6555`	`<para>`
`6558`	`6556`	`Unlike <varname>statement_timeout</>, this timeout can only occur`
`6559`	`6557`	`while waiting for locks. Note that if <varname>statement_timeout</>`
`6560`	`6558`	`is nonzero, it is rather pointless to set <varname>lock_timeout</> to`
`6561`	`6559`	`the same or larger value, since the statement timeout would always`
`6562`		`- trigger first.`
	`6560`	`+ trigger first. If <varname>log_min_error_statement</> is set to`
	`6561`	`+ <literal>ERROR</> or lower, the statement that timed out will be`
	`6562`	`+ logged.`
`6563`	`6563`	`</para>`
`6564`	`6564`
`6565`	`6565`	`<para>`

Comments

(0)