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

Commit4a36eab

Browse files
committed
doc: Add description about re-analysis and re-planning of a prepared statement.
A prepared statement is re-analyzed and re-planned whenever databaseobjects used in the statement have undergone definitional changes orthe planner statistics of them have been updated. The former has beendocumented from before, but the latter was not previously. This commitadds the description about the latter case into the docs.Author: Atsushi TorikoshiReviewed-by: Andy Fan, Fujii MasaoDiscussion:https://postgr.es/m/3ac82f4817c9fe274a905c8a38d87bd9@oss.nttdata.com
1 parentf3a8f73 commit4a36eab

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

‎doc/src/sgml/ref/prepare.sgml

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -184,7 +184,8 @@ EXPLAIN EXECUTE <replaceable>name</replaceable>(<replaceable>parameter_values</r
184184
analysis and planning of the statement, <productname>PostgreSQL</productname> will
185185
force re-analysis and re-planning of the statement before using it
186186
whenever database objects used in the statement have undergone
187-
definitional (DDL) changes since the previous use of the prepared
187+
definitional (DDL) changes or the planner statistics of them have
188+
been updated since the previous use of the prepared
188189
statement. Also, if the value of <xref linkend="guc-search-path"/> changes
189190
from one use to the next, the statement will be re-parsed using the new
190191
<varname>search_path</varname>. (This latter behavior is new as of

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp