diff options
author | David Rowley <drowley@postgresql.org> | 2025-04-02 14:04:31 +1300 |
---|---|---|
committer | David Rowley <drowley@postgresql.org> | 2025-04-02 14:04:31 +1300 |
commit | 2be0fe94bf20e9125a47aa216ee9b07d96ff0fae (patch) | |
tree | 90752dd66ec98516b738bd4f6150498b9cecad75 | |
parent | a7f213b11d92e7a6423821d041e283c4fde6ee5b (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.sgml | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/doc/src/sgml/ddl.sgml b/doc/src/sgml/ddl.sgml index 7f3d7e2c3e8..dd00bbdaa79 100644 --- a/doc/src/sgml/ddl.sgml +++ b/doc/src/sgml/ddl.sgml @@ -4812,7 +4812,9 @@ EXPLAIN SELECT count(*) FROM measurement WHERE logdate >= 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> |