| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql: Rework the stats_ext test |
| Date: | 2017-03-27 15:43:59 |
| Message-ID: | E1csWoJ-0007x4-PM@gemulon.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Rework the stats_ext test
As suggested by Tom Lane, avoid printing specific estimated cost values,
because they vary across architectures; instead, verify plan shapes (in
this case, HashAggregate vs. GroupAggregate), as we do in other planner
tests.
We can now remove expected/stats_ext_1.out.
Author: Tomas Vondra
Branch
------
master
Details
-------
http://git.postgresql.org/pg/commitdiff/bed9ef5a16239d91d97a1fa2efd9309c3cbbc4b2
Modified Files
--------------
src/test/regress/expected/stats_ext.out | 231 ++++++++++++++++++++++++------
src/test/regress/expected/stats_ext_1.out | 155 --------------------
src/test/regress/sql/stats_ext.sql | 83 +++++++++--
3 files changed, 262 insertions(+), 207 deletions(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2017-03-27 15:44:52 | Re: pgsql: Fix a couple of problems in pg_get_statisticsextdef |
| Previous Message | Peter Eisentraut | 2017-03-27 15:39:19 | pgsql: PL/Python: Add cursor and execute methods to plan object |