Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 4a36eab

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 database objects used in the statement have undergone definitional changes or the planner statistics of them have been updated. The former has been documented from before, but the latter was not previously. This commit adds the description about the latter case into the docs. Author: Atsushi Torikoshi Reviewed-by: Andy Fan, Fujii Masao Discussion: https://postgr.es/m/3ac82f4817c9fe274a905c8a38d87bd9@oss.nttdata.com
1 parent f3a8f73 commit 4a36eab

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

doc/src/sgml/ref/prepare.sgml

+2-1
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)