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

Commit 121d774

Browse files
committed
Doc: add information about partition locking
The documentation around locking of partitions for the executor startup phase of run-time partition pruning wasn't clear about which partitions were being locked. Fix that. Reviewed-by: Tender Wang <tndrwang@gmail.com> Discussion: https://postgr.es/m/CAApHDvp738G75HfkKcfXaf3a8s%3D6mmtOLh46tMD0D2hAo1UCzA%40mail.gmail.com Backpatch-through: 13
1 parent b3219c6 commit 121d774

File tree

1 file changed

+7
-1
lines changed

1 file changed

+7
-1
lines changed

doc/src/sgml/ddl.sgml

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5075,7 +5075,13 @@ EXPLAIN SELECT count(*) FROM measurement WHERE logdate &gt;= DATE '2008-01-01';
50755075
It is possible to determine the number of partitions which were
50765076
removed during this phase by observing the
50775077
<quote>Subplans Removed</quote> property in the
5078-
<command>EXPLAIN</command> output.
5078+
<command>EXPLAIN</command> output. The query planner obtains locks for
5079+
all partitions which are part of the plan. However, when the executor
5080+
uses a cached plan, locks are only obtained on the partitions which
5081+
remain after partition pruning done during the initialization phase of
5082+
execution, i.e., the ones shown in the <command>EXPLAIN</command>
5083+
output and not the ones referred to by the
5084+
<quote>Subplans Removed</quote> property.
50795085
</para>
50805086
</listitem>
50815087

0 commit comments

Comments
 (0)