Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Doc: add information about partition locking
authorDavid Rowley <drowley@postgresql.org>
Wed, 2 Apr 2025 01:04:31 +0000 (14:04 +1300)
committerDavid Rowley <drowley@postgresql.org>
Wed, 2 Apr 2025 01:04:31 +0000 (14:04 +1300)
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

doc/src/sgml/ddl.sgml

index 7f3d7e2c3e871c28826fe1b5cfc36a7d6b5d01a4..dd00bbdaa79bdb6cbc25b2dd9ba664fe86294a41 100644 (file)
@@ -4812,7 +4812,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>