diff options
| author | David Rowley <drowley@postgresql.org> | 2024-10-29 23:28:12 +1300 |
|---|---|---|
| committer | David Rowley <drowley@postgresql.org> | 2024-10-29 23:28:12 +1300 |
| commit | 84b8fccbe5c21cc2a05f8cf91903cadc6ebfe680 (patch) | |
| tree | b5b1f7b11d547a5826024ca1817c94943e8952a2 /src/backend/commands/view.c | |
| parent | 014720c6d9fb1285846f0b7cc1c80bdbe887a743 (diff) | |
| download | postgresql-84b8fccbe5c21cc2a05f8cf91903cadc6ebfe680.tar.gz postgresql-84b8fccbe5c21cc2a05f8cf91903cadc6ebfe680.zip | |
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
Diffstat (limited to 'src/backend/commands/view.c')
0 files changed, 0 insertions, 0 deletions