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/[email protected] 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(-)
