From: | David Rowley <drowley(at)postgresql(dot)org> |
---|---|
To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | pgsql: Doc: add detail about EXPLAIN's "Disabled" property |
Date: | 2024-10-29 10:28:35 |
Message-ID: | E1t5jSm-002zgK-9I@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Doc: add detail about EXPLAIN's "Disabled" property
c01743aa4 and later 161320b4b adjusted the EXPLAIN output to show which
plan nodes were chosen despite being disabled by the various enable*
GUCs. Prior to e22253467, the disabledness of a node was only evident by
a large startup cost penalty. Since we now explicitly tag disabled nodes
with a boolean property in EXPLAIN, let's add some documentation to
provide some details about why and when disabled nodes can appear in the
plan.
Author: Laurenz Albe, David Rowley
Discussion: https://postgr.es/m/883729e429267214753d5e438c82c73a58c3db5d.camel@cybertec.at
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/84b8fccbe5c21cc2a05f8cf91903cadc6ebfe680
Modified Files
--------------
doc/src/sgml/perform.sgml | 25 +++++++++++++++++++++++++
1 file changed, 25 insertions(+)
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2024-10-29 12:39:14 | pgsql: Reduce variable scope and possibly useless palloc |
Previous Message | Peter Eisentraut | 2024-10-29 09:33:32 | pgsql: Add missing FATAL => 'all' to a use warnings in Perl |