From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Mon, 3 Sep 2007 01:28:40 +0000 (+0000)
Subject: Add an ORDER BY to nail down the expected row order from a query that's
X-Git-Tag: REL8_3_BETA1~240
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=6f4a5462b4d710316877f21bdad2c13f17e61fe7;p=postgresql

Add an ORDER BY to nail down the expected row order from a query that's
been shown to be sensitive to concurrent autovacuum.  Per Alvaro.
---

diff --git a/src/test/regress/expected/cluster.out b/src/test/regress/expected/cluster.out
index 0eb83369fb..9bf4764b68 100644
--- a/src/test/regress/expected/cluster.out
+++ b/src/test/regress/expected/cluster.out
@@ -249,11 +249,12 @@ SELECT a,b,c,substring(d for 30), length(d) from clstr_tst;
 INSERT INTO clstr_tst (b, c) VALUES (1111, 'this should fail');
 ERROR:  insert or update on table "clstr_tst" violates foreign key constraint "clstr_tst_con"
 DETAIL:  Key (b)=(1111) is not present in table "clstr_tst_s".
-SELECT conname FROM pg_constraint WHERE conrelid = 'clstr_tst'::regclass;
+SELECT conname FROM pg_constraint WHERE conrelid = 'clstr_tst'::regclass
+ORDER BY 1;
     conname     
 ----------------
- clstr_tst_pkey
  clstr_tst_con
+ clstr_tst_pkey
 (2 rows)
 
 SELECT relname, relkind,
diff --git a/src/test/regress/sql/cluster.sql b/src/test/regress/sql/cluster.sql
index 8f4fc58912..a54d6e07f5 100644
--- a/src/test/regress/sql/cluster.sql
+++ b/src/test/regress/sql/cluster.sql
@@ -73,7 +73,8 @@ SELECT a,b,c,substring(d for 30), length(d) from clstr_tst;
 -- Verify that foreign key link still works
 INSERT INTO clstr_tst (b, c) VALUES (1111, 'this should fail');
 
-SELECT conname FROM pg_constraint WHERE conrelid = 'clstr_tst'::regclass;
+SELECT conname FROM pg_constraint WHERE conrelid = 'clstr_tst'::regclass
+ORDER BY 1;
 
 
 SELECT relname, relkind,