aboutsummaryrefslogtreecommitdiff
path: root/src/backend/commands/tablecmds.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
commit068503c76511cdb0080bab689662a20e86b9c845 (patch)
tree3fbbcfd66a6bb57381172da8bd0a7b7dbe370114 /src/backend/commands/tablecmds.c
parent4dbe1969079672064777e71c3fc981abbf55e207 (diff)
downloadpostgresql-068503c76511cdb0080bab689662a20e86b9c845.tar.gz
postgresql-068503c76511cdb0080bab689662a20e86b9c845.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/commands/tablecmds.c')
0 files changed, 0 insertions, 0 deletions