Fixed opr_sanity regression test to ignore the new

RI_FKey_... constrint triggers when looking for illegal
pg_proc entries.

Jan

diff --git a/src/test/regress/expected/opr_sanity.out b/src/test/regress/expected/opr_sanity.out
index e8ce7df..96253c7 100644 (file)
--- a/src/test/regress/expected/opr_sanity.out
+++ b/src/test/regress/expected/opr_sanity.out
@@ -2,7 +2,8 @@ QUERY: SELECT p1.oid, p1.proname
 FROM pg_proc as p1
 WHERE (p1.prolang = 0 OR p1.prorettype = 0 OR
     p1.pronargs < 0 OR p1.pronargs > 9)
-       AND p1.proname !~ '^pl[^_]+_call_handler$';
+       AND p1.proname !~ '^pl[^_]+_call_handler$'
+       AND p1.proname !~ '^RI_FKey_';
 oid|proname
 ---+-------
 (0 rows)

diff --git a/src/test/regress/sql/opr_sanity.sql b/src/test/regress/sql/opr_sanity.sql
index 4548209..8cfc850 100644 (file)
--- a/src/test/regress/sql/opr_sanity.sql
+++ b/src/test/regress/sql/opr_sanity.sql
@@ -27,7 +27,8 @@ SELECT p1.oid, p1.proname
 FROM pg_proc as p1
 WHERE (p1.prolang = 0 OR p1.prorettype = 0 OR
     p1.pronargs < 0 OR p1.pronargs > 9)
-       AND p1.proname !~ '^pl[^_]+_call_handler$';
+       AND p1.proname !~ '^pl[^_]+_call_handler$'
+       AND p1.proname !~ '^RI_FKey_';
 
 -- Look for conflicting proc definitions (same names and input datatypes).