aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistscan.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2019-02-09 21:02:06 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2019-02-09 21:02:06 -0500
commitee6370978fd921c22ec8bf2239ad4d30ae126fed (patch)
treed2c12086577364d00b718a6986d811700a02cb61 /src/backend/access/gist/gistscan.c
parentef9bf359369b4dfaceb859941c3898b5ce1decf6 (diff)
downloadpostgresql-ee6370978fd921c22ec8bf2239ad4d30ae126fed.tar.gz
postgresql-ee6370978fd921c22ec8bf2239ad4d30ae126fed.zip
Solve cross-version-upgrade testing problem induced by 1fb57af92.
Renaming varchar_transform to varchar_support had a side effect I hadn't foreseen: the core regression tests leave around a transform object that relies on that function, so the name change breaks cross-version upgrade tests, because the name used in the older branches doesn't match. Since the dependency on varchar_transform was chosen with the aid of a dartboard anyway (it would surely not work as a language transform support function), fix by just choosing a different random builtin function with the right signature. Also add some comments explaining why this isn't horribly unsafe. I chose to make the same substitution in a couple of other copied-and-pasted test cases, for consistency, though those aren't directly contributing to the testing problem. Per buildfarm. Back-patch, else it doesn't fix the problem.
Diffstat (limited to 'src/backend/access/gist/gistscan.c')
0 files changed, 0 insertions, 0 deletions