Commitf872f18

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 parent021065a commitf872f18Copy full SHA for f872f18

File tree

-4

lines changed

-4

lines changed

Lines changed: 4 additions & 4 deletions

Original file line number	Diff line number	Diff line change
`@@ -6855,17 +6855,17 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv;`
`6855`	`6855`	`each lock acquisition attempt. The limit applies both to explicit`
`6856`	`6856`	`locking requests (such as <command>LOCK TABLE</command>, or <command>SELECT`
`6857`	`6857`	`FOR UPDATE</command> without <literal>NOWAIT</literal>) and to implicitly-acquired`
`6858`		`- locks. If <varname>log_min_error_statement</varname> is set to`
`6859`		`- <literal>ERROR</literal> or lower, the statement that timed out will be`
`6860`		`- logged. A value of zero (the default) turns this off.`
	`6858`	`+ locks. A value of zero (the default) turns this off.`
`6861`	`6859`	`</para>`
`6862`	`6860`
`6863`	`6861`	`<para>`
`6864`	`6862`	`Unlike <varname>statement_timeout</varname>, this timeout can only occur`
`6865`	`6863`	`while waiting for locks. Note that if <varname>statement_timeout</varname>`
`6866`	`6864`	`is nonzero, it is rather pointless to set <varname>lock_timeout</varname> to`
`6867`	`6865`	`the same or larger value, since the statement timeout would always`
`6868`		`- trigger first.`
	`6866`	`+ trigger first. If <varname>log_min_error_statement</varname> is set to`
	`6867`	`+ <literal>ERROR</literal> or lower, the statement that timed out will be`
	`6868`	`+ logged.`
`6869`	`6869`	`</para>`
`6870`	`6870`
`6871`	`6871`	`<para>`

Comments

(0)