diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2019-12-11 17:05:30 -0500 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2019-12-11 17:05:30 -0500 |
| commit | 5935917ce59e2e613ac7a4b54ed49a7b9f8f28ac (patch) | |
| tree | b89e6f02a9c226b1e6e94ddf8b3de73afd64a761 /src/backend/access/gist/gist.c | |
| parent | 6ef77cf46e81f45716ec981cb08781d426181378 (diff) | |
| download | postgresql-5935917ce59e2e613ac7a4b54ed49a7b9f8f28ac.tar.gz postgresql-5935917ce59e2e613ac7a4b54ed49a7b9f8f28ac.zip | |
Allow executor startup pruning to prune all child nodes.
Previously, if the startup pruning logic proved that all child nodes
of an Append or MergeAppend could be pruned, we still kept one, just
to keep EXPLAIN from failing. The previous commit removed the
ruleutils.c limitation that required this kluge, so drop it. That
results in less-confusing EXPLAIN output, as per a complaint from
Yuzuko Hosoya.
David Rowley
Discussion: https://postgr.es/m/001001d4f44b$2a2cca50$7e865ef0$@lab.ntt.co.jp
Diffstat (limited to 'src/backend/access/gist/gist.c')
0 files changed, 0 insertions, 0 deletions