aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistutil.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2014-06-26 10:41:10 -0700
committerTom Lane <tgl@sss.pgh.pa.us>2014-06-26 10:42:08 -0700
commit555d0b2000e33fd1ad2721015996a66c43bbb3cd (patch)
tree5fd992cd25c52f5b33634250dbfa21a5652e71a4 /src/backend/access/gist/gistutil.c
parent865868043af0f23cd72d4450ca4410828b016cea (diff)
downloadpostgresql-555d0b2000e33fd1ad2721015996a66c43bbb3cd.tar.gz
postgresql-555d0b2000e33fd1ad2721015996a66c43bbb3cd.zip
Back-patch "Fix EquivalenceClass processing for nested append relations".
When we committed a87c729153e372f3731689a7be007bc2b53f1410, we somehow failed to notice that it didn't merely improve plan quality for expression indexes; there were very closely related cases that failed outright with "could not find pathkey item to sort". The failing cases seem to be those where the planner was already capable of selecting a MergeAppend plan, and there was inheritance involved: the lack of appropriate eclass child members would prevent prepare_sort_from_pathkeys() from succeeding on the MergeAppend's child plan nodes for inheritance child tables. Accordingly, back-patch into 9.1 through 9.3, along with an extra regression test case covering the problem. Per trouble report from Michael Glaesemann.
Diffstat (limited to 'src/backend/access/gist/gistutil.c')
0 files changed, 0 insertions, 0 deletions