Hm, seems my hack on rowtypes regression test has made its output row

order platform-specific.  Add an ORDER BY clause to stop buildfarm
failures.

2 files changed, 5 insertions, 3 deletions

diff --git a/src/test/regress/expected/rowtypes.out b/src/test/regress/expected/rowtypes.out
index 8d3f5dffb15..dbf163cd695 100644
--- a/src/test/regress/expected/rowtypes.out
+++ b/src/test/regress/expected/rowtypes.out
@@ -207,11 +207,12 @@ HINT:  Row comparison operators must be associated with btree operator families.
 -- Check row comparison with a subselect
 select unique1, unique2 from tenk1
 where (unique1, unique2) < any (select ten, ten from tenk1 where hundred < 3)
-  and unique1 <= 20;
+      and unique1 <= 20
+order by 1;
  unique1 | unique2 
 ---------+---------
-       1 |    2838
        0 |    9998
+       1 |    2838
 (2 rows)
 
 -- Also check row comparison with an indexable condition
diff --git a/src/test/regress/sql/rowtypes.sql b/src/test/regress/sql/rowtypes.sql
index 1b68bad7a5e..779b20e8631 100644
--- a/src/test/regress/sql/rowtypes.sql
+++ b/src/test/regress/sql/rowtypes.sql
@@ -101,7 +101,8 @@ select ROW('ABC','DEF') ~~ ROW('DEF','ABC') as fail;
 -- Check row comparison with a subselect
 select unique1, unique2 from tenk1
 where (unique1, unique2) < any (select ten, ten from tenk1 where hundred < 3)
-  and unique1 <= 20;
+      and unique1 <= 20
+order by 1;
 
 -- Also check row comparison with an indexable condition
 select thousand, tenthous from tenk1