Stabilize order of results in insert regresion test

Same issue as in c2392efc83, but in different regression test. Fixed the
same way, i.e. by adding ORDER BY clauses to stabilize the order.

diff --git a/src/test/regress/expected/insert.out b/src/test/regress/expected/insert.out
index 58b345f50a9dbed05666e862b2504aca5b70e975..a8b5fb63a6ba81e4630c4590941dd584b0c2a08a 100644 (file)
--- a/src/test/regress/expected/insert.out
+++ b/src/test/regress/expected/insert.out
@@ -251,7 +251,7 @@ insert into range_parted values ('b', 10);
 insert into range_parted values ('a');
 ERROR:  no partition of relation "range_parted" found for row
 DETAIL:  Partition key of the failing row contains (a, (b + 0)) = (a, null).
-select tableoid::regclass, * from range_parted;
+select tableoid::regclass, * from range_parted order by 1, 2, 3;
  tableoid | a | b  
 ----------+---+----
  part1    | a |  1
@@ -476,17 +476,17 @@ insert into mcrparted4 values (30, 21, 20);       -- error
 ERROR:  new row for relation "mcrparted4" violates partition constraint
 DETAIL:  Failing row contains (30, 21, 20).
 -- check rows
-select tableoid::regclass::text, * from mcrparted order by 1;
+select tableoid::regclass::text, * from mcrparted order by 1, 2, 3, 4;
   tableoid  | a  |  b   |  c   
 ------------+----+------+------
  mcrparted0 |  0 |    1 |    1
  mcrparted0 |  0 |    1 |    1
+ mcrparted1 |  2 |    1 |    0
+ mcrparted1 |  2 |    1 |    0
  mcrparted1 |  9 | 1000 |    1
  mcrparted1 |  9 | 1000 |    1
  mcrparted1 | 10 |    5 |   -1
  mcrparted1 | 10 |    5 |   -1
- mcrparted1 |  2 |    1 |    0
- mcrparted1 |  2 |    1 |    0
  mcrparted2 | 10 |    6 | 1000
  mcrparted2 | 10 |    6 | 1000
  mcrparted2 | 10 | 1000 | 1000

diff --git a/src/test/regress/sql/insert.sql b/src/test/regress/sql/insert.sql
index 80e1da4be79b5a78b4d15f57ce296a609d384bd7..12d6b3dc8ee5a7a81351615299bb5b18ecb987f1 100644 (file)
--- a/src/test/regress/sql/insert.sql
+++ b/src/test/regress/sql/insert.sql
@@ -154,7 +154,7 @@ insert into range_parted values ('b', 1);
 insert into range_parted values ('b', 10);
 -- fail (partition key (b+0) is null)
 insert into range_parted values ('a');
-select tableoid::regclass, * from range_parted;
+select tableoid::regclass, * from range_parted order by 1, 2, 3;
 
 -- ok
 insert into list_parted values (null, 1);
@@ -328,7 +328,7 @@ insert into mcrparted5 values (30, 21, 20);
 insert into mcrparted4 values (30, 21, 20);    -- error
 
 -- check rows
-select tableoid::regclass::text, * from mcrparted order by 1;
+select tableoid::regclass::text, * from mcrparted order by 1, 2, 3, 4;
 
 -- cleanup
 drop table mcrparted;