You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Add ORDER BY to a query to prevent occasional regression test failures.
Per buildfarm, we sometimes get row-ordering variations in the output.This also makes this query look more like numerous other ones in the sametest file.
Copy file name to clipboardExpand all lines: src/test/regress/expected/inherit.out
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -601,7 +601,7 @@ create table p1(ff1 int);
601
601
alter table only p1 add constraint p1chk check (ff1 > 0);
602
602
alter table p1 add constraint p2chk check (ff1 > 10);
603
603
-- conisonly should be true for ONLY constraint
604
-
select pc.relname, pgc.conname, pgc.contype, pgc.conislocal, pgc.coninhcount, pgc.conisonly from pg_class as pc inner join pg_constraint as pgc on (pgc.conrelid = pc.oid) where pc.relname = 'p1';
604
+
select pc.relname, pgc.conname, pgc.contype, pgc.conislocal, pgc.coninhcount, pgc.conisonly from pg_class as pc inner join pg_constraint as pgc on (pgc.conrelid = pc.oid) where pc.relname = 'p1' order by 1,2;