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

diff --git a/src/bin/pg_upgrade/test.sh b/src/bin/pg_upgrade/test.sh
index a2da1abe3f167324d3194bfc1fe8d289bc6da99c..8b13ec8692d041df6958baa4a5850c29631dae51 100644 (file)
--- 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