summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDavid Rowley2025-04-02 01:03:48 +0000
committerDavid Rowley2025-04-02 01:03:48 +0000
commite962d6d12b7e8185775da26ef0f77a3ac63d18a0 (patch)
tree71b9b743b1564c29fb9708fac552df5230f90aaf
parent5672a839977949457d1f81a4fd43b1e7c097ba14 (diff)
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
-rw-r--r--doc/src/sgml/ddl.sgml4
1 files changed, 3 insertions, 1 deletions
diff --git a/doc/src/sgml/ddl.sgml b/doc/src/sgml/ddl.sgml
index c150dd217f9..bef12758711 100644
--- a/doc/src/sgml/ddl.sgml
+++ b/doc/src/sgml/ddl.sgml
@@ -4986,7 +4986,9 @@ EXPLAIN SELECT count(*) FROM measurement WHERE logdate &gt;= DATE '2008-01-01';
It is possible to determine the number of partitions which were
removed during this phase by observing the
<quote>Subplans Removed</quote> property in the
- <command>EXPLAIN</command> output.
+ <command>EXPLAIN</command> output. It's important to note that any
+ partitions removed by the partition pruning done at this stage are
+ still locked at the beginning of execution.
</para>
</listitem>