resolve failures in 'gist' test suite by making them deterministic

As described in e39c4afcfa, the results were platform dependent.

diff --git a/src/test/regress/expected/gist.out b/src/test/regress/expected/gist.out
index 7574ec9fe0328d71d90432342736222854009845..ca6adb869c2f27f10188c4848da9b20c008b71fe 100644 (file)
--- a/src/test/regress/expected/gist.out
+++ b/src/test/regress/expected/gist.out
@@ -63,13 +63,13 @@ select p from gist_tbl where p <@ box(point(0,0), point(0.5, 0.5));
 -- Also test an index-only knn-search
 explain (costs off)
 select p from gist_tbl where p <@ box(point(0,0), point(0.5, 0.5))
-order by p <-> point(0.2, 0.2);
+order by p <-> point(0.201, 0.201);
                           QUERY PLAN                          
 --------------------------------------------------------------
  Remote Subquery Scan on all (datanode_1,datanode_2)
    ->  Index Only Scan using gist_tbl_point_index on gist_tbl
          Index Cond: (p <@ '(0.5,0.5),(0,0)'::box)
-         Order By: (p <-> '(0.2,0.2)'::point)
+         Order By: (p <-> '(0.201,0.201)'::point)
 (4 rows)
 
 select p from gist_tbl where p <@ box(point(0,0), point(0.5, 0.5))
@@ -92,13 +92,13 @@ order by p <-> point(0.201, 0.201);
 -- Check commuted case as well
 explain (costs off)
 select p from gist_tbl where p <@ box(point(0,0), point(0.5, 0.5))
-order by point(0.1, 0.1) <-> p;
+order by point(0.101, 0.101) <-> p;
                           QUERY PLAN                          
 --------------------------------------------------------------
  Remote Subquery Scan on all (datanode_1,datanode_2)
    ->  Index Only Scan using gist_tbl_point_index on gist_tbl
          Index Cond: (p <@ '(0.5,0.5),(0,0)'::box)
-         Order By: (p <-> '(0.1,0.1)'::point)
+         Order By: (p <-> '(0.101,0.101)'::point)
 (4 rows)
 
 select p from gist_tbl where p <@ box(point(0,0), point(0.5, 0.5))