Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit8303a3d

Browse files
committed
Mention that log_statement only prints query on PREPARE, not EXECUTE,
and PL/pgSQL only prints queries on first function call.
1 parent9d88880 commit8303a3d

File tree

1 file changed

+6
-3
lines changed

1 file changed

+6
-3
lines changed

‎doc/src/sgml/runtime.sgml

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
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 $
33
-->
44

55
<Chapter Id="runtime">
@@ -1822,8 +1822,11 @@ SET ENABLE_SEQSCAN TO OFF;
18221822
<listitem>
18231823
<para>
18241824
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.
18271830
</para>
18281831
</listitem>
18291832
</varlistentry>

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp