mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fixed opr_sanity regression test to ignore the new

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

Jan
This commit is contained in:
Jan Wieck 1999-09-30 15:28:34 +00:00
parent ccecf1fa46
commit ce1f5ed547
2 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
src/test/regress/expected/opr_sanity.out
View File

@ -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)

3
src/test/regress/sql/opr_sanity.sql
View File

@ -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).