Skip to content
Snippets Groups Projects
Commit 8303a3d1 authored by Bruce Momjian's avatar Bruce Momjian
Browse files

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

and PL/pgSQL only prints queries on first function call.
parent 9d888807
No related branches found
No related tags found
No related merge requests found
<!-- <!--
$PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.232 2004/01/23 23:54:20 tgl Exp $ $PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.233 2004/01/25 00:36:18 momjian Exp $
--> -->
<Chapter Id="runtime"> <Chapter Id="runtime">
...@@ -1822,8 +1822,11 @@ SET ENABLE_SEQSCAN TO OFF; ...@@ -1822,8 +1822,11 @@ SET ENABLE_SEQSCAN TO OFF;
<listitem> <listitem>
<para> <para>
Causes each SQL statement to be logged. The default is off. Causes each SQL statement to be logged. The default is off.
Only superusers can turn off this option if it is enabled by <command>EXECUTE</> only displays the plan name, not the
the administrator. prepared query. Server-side languages like
<application>PL/pgSQL</> that store functions in a cache only
display their queries on first function call. superusers can
turn off this option if it is enabled by the administrator.
</para> </para>
</listitem> </listitem>
</varlistentry> </varlistentry>
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment