pgsql: Fix EXPLAIN MERGE output when no tuples are processed

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Fix EXPLAIN MERGE output when no tuples are processed
Date: 2022-05-18 19:21:48
Message-ID: E1nrPEx-001MoT-RJ@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Fix EXPLAIN MERGE output when no tuples are processed

An 'else' clause was misplaced in commit 598ac10be1c2, making zero-rows
output look a bit silly. Add a test case for it.

Pointed out by Tom Lane.

Discussion: https://postgr.es/m/21030.1652893083@sss.pgh.pa.us

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/12e423e21d8ef47d95a099c12f625f6d191eaf92

Modified Files
--------------
src/backend/commands/explain.c | 27 +++++++++++++++------------
src/test/regress/expected/merge.out | 20 +++++++++++++++++++-
src/test/regress/sql/merge.sql | 8 +++++++-
3 files changed, 41 insertions(+), 14 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2022-05-18 20:02:21 Re: pgsql: Check column list length in XMLTABLE/JSON_TABLE alias
Previous Message Alvaro Herrera 2022-05-18 18:44:52 pgsql: Check column list length in XMLTABLE/JSON_TABLE alias