aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeHashjoin.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2019-11-13 11:35:37 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2019-11-13 11:35:37 -0500
commit29aeda6e4e609b66b6f1c3c73b4def6fb34d90ed (patch)
treef3221ac7ad2238132a13de2e2fe4bc796c927b9e /src/backend/executor/nodeHashjoin.c
parent7b8a899bdeb638f46e102d1714c079a0874e9fa0 (diff)
downloadpostgresql-29aeda6e4e609b66b6f1c3c73b4def6fb34d90ed.tar.gz
postgresql-29aeda6e4e609b66b6f1c3c73b4def6fb34d90ed.zip
Handle arrays and ranges in pg_upgrade's test for non-upgradable types.
pg_upgrade needs to check whether certain non-upgradable data types appear anywhere on-disk in the source cluster. It knew that it has to check for these types being contained inside domains and composite types; but it somehow overlooked that they could be contained in arrays and ranges, too. Extend the existing recursive-containment query to handle those cases. We probably should have noticed this oversight while working on commit 0ccfc2822 and follow-ups, but we failed to :-(. The whole thing's possibly a bit overdesigned, since we don't really expect that any of these types will appear on disk; but if we're going to the effort of doing a recursive search then it's silly not to cover all the possibilities. While at it, refactor so that we have only one copy of the search logic, not three-and-counting. Also, to keep the branches looking more alike, back-patch the output wording change of commit 1634d3615. Back-patch to all supported branches. Discussion: https://postgr.es/m/31473.1573412838@sss.pgh.pa.us
Diffstat (limited to 'src/backend/executor/nodeHashjoin.c')
0 files changed, 0 insertions, 0 deletions