Re: XversionUpgrade tests broken by postfix operator removal
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
Cc: pgsql-hackers@lists.postgresql.org, pgbf@twiska.com
Date: 2020-09-18T20:25:45Z
Lists: pgsql-hackers
Andrew Dunstan <andrew.dunstan@2ndquadrant.com> writes: > On 9/18/20 10:39 AM, Tom Lane wrote: >> I intentionally let that happen, figuring that it'd be good to get some >> buildfarm cycles on the new code in pg_upgrade that does this check. >> But now we have to think about updating the test. I think the best >> bet is just to add some DROP OPERATOR commands to the existing >> cleanup logic in TestUpgradeXversion.pm. It looks like this would >> do the trick: >> >> drop operator #@# (bigint,NONE); >> drop operator #%# (bigint,NONE); >> drop operator !=- (bigint,NONE); >> drop operator #@%# (bigint,NONE); > Almost. I had to remove one more operator. Hmm, that's not a postfix operator ... oh, it's because it depends on the numeric_fac function alias which we also removed. We could eliminate the need to drop it if we changed the definition to use "factorial" instead of "numeric_fac" in all the back branches. Not sure if that's a better solution or not. Might be worth doing, because in the older branches that's the only user-defined prefix operator, so we're missing some pg_upgrade test coverage if we just drop it. regards, tom lane
Commits
-
In pg_upgrade cross-version test, handle postfix operators.
- fa744697c791 14.0 landed
-
Use factorial rather than numeric_fac in create_operator.sql.
- cc7b27da7fb8 11.10 landed
- a950fb073426 10.15 landed
- 9ab5ed4194f3 13.0 landed
- 760b8fe766bc 9.5.24 landed
- 1e00333ffa2e 9.6.20 landed
- 1af91dc032cf 12.5 landed
-
Remove support for postfix (right-unary) operators.
- 1ed6b895634c 14.0 cited