aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNoah Misch <noah@leadboat.com>2020-12-30 01:43:43 -0800
committerNoah Misch <noah@leadboat.com>2020-12-30 01:43:43 -0800
commitfa744697c79189a661f802d9a979d959b4454df0 (patch)
tree5638df10a2ffb6d385c858c9c9b2a317e5354f60
parent52202bb396b1e96c43bfd767d6e434b1c6fd2ae1 (diff)
downloadpostgresql-fa744697c79189a661f802d9a979d959b4454df0.tar.gz
postgresql-fa744697c79189a661f802d9a979d959b4454df0.zip
In pg_upgrade cross-version test, handle postfix operators.
Commit 1ed6b895634ce0dc5fd4bd040e87252b32182cba eliminated support for them, so drop them from regression databases before upgrading. This is necessary but not sufficient for testing v13 -> v14 upgrades. Discussion: https://postgr.es/m/449144.1600439950@sss.pgh.pa.us
-rw-r--r--src/bin/pg_upgrade/test.sh7
1 files changed, 6 insertions, 1 deletions
diff --git a/src/bin/pg_upgrade/test.sh b/src/bin/pg_upgrade/test.sh
index a2da1abe3f1..8b13ec8692d 100644
--- a/src/bin/pg_upgrade/test.sh
+++ b/src/bin/pg_upgrade/test.sh
@@ -177,7 +177,12 @@ if "$MAKE" -C "$oldsrc" installcheck-parallel; then
esac
fix_sql="$fix_sql
DROP FUNCTION IF EXISTS
- public.oldstyle_length(integer, text); -- last in 9.6";
+ public.oldstyle_length(integer, text); -- last in 9.6
+ DROP OPERATOR IF EXISTS -- last in v13
+ public.#@# (pg_catalog.int8, NONE),
+ public.#%# (pg_catalog.int8, NONE),
+ public.!=- (pg_catalog.int8, NONE),
+ public.#@%# (pg_catalog.int8, NONE);"
psql -X -d regression -c "$fix_sql;" || psql_fix_sql_status=$?
fi