| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | pgsql: Try to stabilize results of new tuplesort regression test. |
| Date: | 2019-12-14 20:02:02 |
| Message-ID: | E1igDc2-0003aw-QF@gemulon.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Try to stabilize results of new tuplesort regression test.
It appears that a concurrent autovacuum/autoanalyze run can cause
changes in the plans expected by this test. To prevent that, change
the tables it uses to be temp tables --- there's no need for them
to be permanent, and this should save a few cycles too.
Discussion: https://postgr.es/m/3244.1576160824@sss.pgh.pa.us
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/baa32ce28b39eccdf384e979dac5ad8be91ff44e
Modified Files
--------------
src/test/regress/expected/tuplesort.out | 9 ++-------
src/test/regress/sql/tuplesort.sql | 11 ++---------
2 files changed, 4 insertions(+), 16 deletions(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2019-12-15 13:06:41 | pgsql: Remove duplicated progress reporting during heap scan of VACUUM |
| Previous Message | Tom Lane | 2019-12-14 18:50:55 | pgsql: Prevent overly-aggressive collapsing of joins to RTE_RESULT rela |