aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeFunctionscan.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2004-02-29 17:36:05 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2004-02-29 17:36:05 +0000
commit64917ccb561e52aac4efa07eabc6f653d296b1dc (patch)
treec47a4944abfd81544ba5c5d3ba0445b99e521051 /src/backend/executor/nodeFunctionscan.c
parente3f27c18474bd1ce5b9044f75f8f4fab6b3c4f18 (diff)
downloadpostgresql-64917ccb561e52aac4efa07eabc6f653d296b1dc.tar.gz
postgresql-64917ccb561e52aac4efa07eabc6f653d296b1dc.zip
make_sort_from_pathkeys()'s method for choosing which of several
equivalent sort expressions to use was broken: you can't just look at the relation membership, you have to actually grovel over the individual Vars in each expression. I think this did work when it was written, but it was broken by subsequent optimizations that made join relations not propagate every single input variable upward. Must find the Var that got propagated, not choose one at random. Per bug report from Daniel O'Neill.
Diffstat (limited to 'src/backend/executor/nodeFunctionscan.c')
0 files changed, 0 insertions, 0 deletions