Commit8303a3d

committed

Mention that log_statement only prints query on PREPARE, not EXECUTE,

and PL/pgSQL only prints queries on first function call.

1 parent9d88880 commit8303a3dCopy full SHA for 8303a3d

File tree

-3

lines changed

-3

lines changed

Lines changed: 6 additions & 3 deletions

Original file line number	Diff line number	Diff line change
`@@ -1,5 +1,5 @@`
`1`	`1`	`<!--`
`2`		`-$PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.232 2004/01/23 23:54:20 tgl Exp $`
	`2`	`+$PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.233 2004/01/25 00:36:18 momjian Exp $`
`3`	`3`	`-->`
`4`	`4`
`5`	`5`	`<Chapter Id="runtime">`
`@@ -1822,8 +1822,11 @@ SET ENABLE_SEQSCAN TO OFF;`
`1822`	`1822`	`<listitem>`
`1823`	`1823`	`<para>`
`1824`	`1824`	`Causes each SQL statement to be logged. The default is off.`
`1825`		`- Only superusers can turn off this option if it is enabled by`
`1826`		`- the administrator.`
	`1825`	`+ <command>EXECUTE</> only displays the plan name, not the`
	`1826`	`+ prepared query. Server-side languages like`
	`1827`	`+ <application>PL/pgSQL</> that store functions in a cache only`
	`1828`	`+ display their queries on first function call. superusers can`
	`1829`	`+ turn off this option if it is enabled by the administrator.`
`1827`	`1830`	`</para>`
`1828`	`1831`	`</listitem>`
`1829`	`1832`	`</varlistentry>`

Comments

(0)