pgsql: Try to stabilize EXPLAIN output in partition_check test. - Mailing list pgsql-committers

From Robert Haas
Subject pgsql: Try to stabilize EXPLAIN output in partition_check test.
Date
Msg-id E1eorKV-0002m0-L7@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Try to stabilize EXPLAIN output in partition_check test.

Commit 7d8ac9814bc9bb6df2d845dbabed38d7284c7c2c adjusted these
tests in the hope of preserving the plan shape, but I failed to
notice that the three partitions were, on my local machine, choosing
two different plan shapes.  This is probably related to the fact
that all three tables have exactly the same row count.  Try to
improve the situation by making pht1_e about half as large as
the other two.

Per Tom Lane and the buildfarm.

Discussion: http://postgr.es/m/25380.1519277713@sss.pgh.pa.us

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/9a5c4f58f36dc7c87619602a7a2ec7de5a287068

Modified Files
--------------
src/test/regress/expected/partition_join.out | 58 +++++++++++++---------------
src/test/regress/sql/partition_join.sql      |  2 +-
2 files changed, 27 insertions(+), 33 deletions(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pgsql: Charge cpu_tuple_cost * 0.5 for Append and MergeAppend nodes.
Next
From: Robert Haas
Date:
Subject: pgsql: Avoid another valgrind complaint about write() of uninitalizedb