pgsql: Fix unstable partition_prune regression tests

From: David Rowley <drowley(at)postgresql(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Fix unstable partition_prune regression tests
Date: 2020-11-02 06:59:37
Message-ID: E1kZToX-00017C-Ep@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Fix unstable partition_prune regression tests

This was broken recently by a929e17e5. I'd failed to remember that
parallel tests should have their EXPLAIN output run through the
explain_parallel_append function so that the output is stable when
parallel workers fail to start.

fairywren was first to notice.

Reported-by: Michael Paquier
Discussion: https://postgr.es/m/20201102062951.GB15770@paquier.xyz

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/90d8f1b1826ce076a502a43fe7c88423b46c6349

Modified Files
--------------
src/test/regress/expected/partition_prune.out | 45 +++++++++++++--------------
src/test/regress/sql/partition_prune.sql | 9 +++---
2 files changed, 26 insertions(+), 28 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Heikki Linnakangas 2020-11-02 10:57:49 pgsql: doc: Mention UNION/ORDER BY etc. keywords in section headers.
Previous Message David Rowley 2020-11-02 06:44:23 Re: pgsql: Allow run-time pruning on nested Append/MergeAppend nodes