aboutsummaryrefslogtreecommitdiff
path: root/src/backend/commands/aggregatecmds.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
commit7cbfd8eb166dd7ab06201f29b72a467233fd7c43 (patch)
tree61fe40be9b81deff2335551293090185679bcb0c /src/backend/commands/aggregatecmds.c
parent73668c590cf5c5719ac0d0481201fd4fd79454bb (diff)
downloadpostgresql-7cbfd8eb166dd7ab06201f29b72a467233fd7c43.tar.gz
postgresql-7cbfd8eb166dd7ab06201f29b72a467233fd7c43.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/aggregatecmds.c')
0 files changed, 0 insertions, 0 deletions