summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDavid Rowley2025-04-02 01:04:53 +0000
committerDavid Rowley2025-04-02 01:04:53 +0000
commitd501e7ba5e50b86a3769595d5cfbfea281312af6 (patch)
tree894e63830f5efa90e4df30eba8aa927b128ad96a
parentb68f664bb024330d33983b1e1f59f483bdd3aca1 (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 40da56923d9..5c98f4e2a3d 100644
--- a/doc/src/sgml/ddl.sgml
+++ b/doc/src/sgml/ddl.sgml
@@ -4690,7 +4690,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>