diff options
| author | Tom Lane | 2014-06-05 01:31:41 +0000 |
|---|---|---|
| committer | Tom Lane | 2014-06-05 01:31:41 +0000 |
| commit | d4d48a5edd9eb28a7f2ee2e4cbe20d984274982e (patch) | |
| tree | 5e494523f05812d6cf8b44d59c7421426fc53c29 /src/test/regress/expected/pg_lsn.out | |
| parent | 4c8ab1b91d2bd154031f7bc8529b9e6e2f1cc443 (diff) | |
Tweak new regression test case for better portability.
Buildfarm says we get different plans on 32-bit and 64-bit platforms,
probably because of MAXALIGN-related differences in memory-consumption
calculations. Add some dummy WHERE clauses so that the planner estimates
different sizes for the three generate_series() relations; that should
stabilize the choice of join order.
Diffstat (limited to 'src/test/regress/expected/pg_lsn.out')
| -rw-r--r-- | src/test/regress/expected/pg_lsn.out | 8 |
1 files changed, 6 insertions, 2 deletions
diff --git a/src/test/regress/expected/pg_lsn.out b/src/test/regress/expected/pg_lsn.out index 493eb9ea840..2854cfd7b94 100644 --- a/src/test/regress/expected/pg_lsn.out +++ b/src/test/regress/expected/pg_lsn.out @@ -70,6 +70,7 @@ SELECT DISTINCT (i || '/' || j)::pg_lsn f FROM generate_series(1, 10) i, generate_series(1, 10) j, generate_series(1, 5) k + WHERE i <= 10 AND j > 0 AND j <= 10 ORDER BY f; QUERY PLAN -------------------------------------------------------------------------- @@ -81,14 +82,17 @@ SELECT DISTINCT (i || '/' || j)::pg_lsn f -> Function Scan on generate_series k -> Materialize -> Nested Loop - -> Function Scan on generate_series i -> Function Scan on generate_series j -(10 rows) + Filter: ((j > 0) AND (j <= 10)) + -> Function Scan on generate_series i + Filter: (i <= 10) +(12 rows) SELECT DISTINCT (i || '/' || j)::pg_lsn f FROM generate_series(1, 10) i, generate_series(1, 10) j, generate_series(1, 5) k + WHERE i <= 10 AND j > 0 AND j <= 10 ORDER BY f; f ------- |