diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2010-11-08 15:15:02 -0500 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2010-11-08 15:15:02 -0500 |
commit | 947d0c862c895618a874344322e7b07c9df05cb2 (patch) | |
tree | d93d5d236afc198144305ee6bedee2b78b6bfff0 /src/backend/storage/file/fd.c | |
parent | 543d22fc7423747afd59fe7214f2ddf6259efc62 (diff) | |
download | postgresql-947d0c862c895618a874344322e7b07c9df05cb2.tar.gz postgresql-947d0c862c895618a874344322e7b07c9df05cb2.zip |
Use appendrel planning logic for top-level UNION ALL structures.
Formerly, we could convert a UNION ALL structure inside a subquery-in-FROM
into an appendrel, as a side effect of pulling up the subquery into its
parent; but top-level UNION ALL always caused use of plan_set_operations().
That didn't matter too much because you got an Append-based plan either
way. However, now that the appendrel code can do things with MergeAppend,
it's worthwhile to hack up the top-level case so it also uses appendrels.
This is a bit of a stopgap; but going much further than this will require
a major rewrite of the planner's set-operations support, which I'm not
prepared to undertake now. For the moment let's grab the low-hanging fruit.
Diffstat (limited to 'src/backend/storage/file/fd.c')
0 files changed, 0 insertions, 0 deletions