Re: array_cat anycompatible change is breaking xversion upgrade tests
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2020-11-08T23:47:22Z
Lists: pgsql-hackers
Attachments
- xversion-fix-head.patch (text/x-diff) patch
- xversion-fix-back.patch (text/x-diff) patch
I wrote: > I think the most plausible response is to add this aggregate to the filter > logic that already exists in the xversion tests. Perhaps we could > alternatively change this test case so that it relies on some other > polymorphic function, but I'm not quite sure what a good candidate > would be. After looking at the commit that added array_cat_accum() (65d9aedb1), I decided that it's fine to replace this aggregate with one using another anyarray function, such as array_larger(). The point of that test is just to show that the array argument can be array-of-record, so we don't need the operation to be array_cat() specifically. So I propose the attached patches to un-break the xversion tests. I'll hold off pushing this till after this week's wraps, though. regards, tom lane
Commits
-
doc: add PG 14 relnote item about array function references
- 25dfb5a831a1 14.0 landed
-
Work around cross-version-upgrade issues created by commit 9e38c2bb5.
- d3d4f7233a3e 11.11 landed
- cea97d98f167 9.6.21 landed
- 97f73a978fc1 14.0 landed
- 6c91e28224f6 9.5.25 landed
- 5ce51f8280d3 12.6 landed
- 5c456d308071 13.2 landed
- 253f02c46f0e 10.16 landed