diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2019-02-09 21:02:06 -0500 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2019-02-09 21:02:06 -0500 |
commit | 1afcf6aed73997c8beb340195a37cf5939c9eb2e (patch) | |
tree | b6c1b4e5a5d23213383b73719f2c2aa6719840f4 /src/backend/executor/execMain.c | |
parent | 2c833217713776d8606fb94e9ab3877d102b86a6 (diff) | |
download | postgresql-1afcf6aed73997c8beb340195a37cf5939c9eb2e.tar.gz postgresql-1afcf6aed73997c8beb340195a37cf5939c9eb2e.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/executor/execMain.c')
0 files changed, 0 insertions, 0 deletions