aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistproc.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2011-04-09 14:40:09 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2011-04-09 14:40:09 -0400
commita19002d4e5da028ff7280554b281e402c609898b (patch)
treeac25f9dab75856d24d88a3a2bfac5faf34c25fba /src/backend/access/gist/gistproc.c
parent7c76906b7e24d9ea94a2b0e33396ebcac600437d (diff)
downloadpostgresql-a19002d4e5da028ff7280554b281e402c609898b.tar.gz
postgresql-a19002d4e5da028ff7280554b281e402c609898b.zip
Adjust collation determination rules as per discussion.
Remove crude hack that tried to propagate collation through a function-returning-record, ie, from the function's arguments to individual fields selected from its result record. That is just plain inconsistent, because the function result is composite and cannot have a collation; and there's no hope of making this kind of action-at-a-distance work consistently. Adjust regression test cases that expected this to happen. Meanwhile, the behavior of casting to a domain with a declared collation stays the same as it was, since that seemed to be the consensus.
Diffstat (limited to 'src/backend/access/gist/gistproc.c')
0 files changed, 0 insertions, 0 deletions