From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | pgsql: Make EXPLAIN MERGE output format more compact |
Date: | 2022-05-18 16:34:56 |
Message-ID: | E1nrMdU-001LMM-G3@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Make EXPLAIN MERGE output format more compact
We can use a single line to print all tuple counts that MERGE processed,
for conciseness, and elide those that are zeroes. Non-text formats
report all numbers, as is typical.
Per comment from Justin Pryzby <pryzby(at)telsasoft(dot)com>
Discussion: https://postgr.es/m/20220511163350.GL19626@telsasoft.com
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/598ac10be1c20961baac44db773eb826f788fdfa
Modified Files
--------------
src/backend/commands/explain.c | 25 +++++++++++++++++++++----
src/test/regress/expected/merge.out | 35 ++++++++++-------------------------
2 files changed, 31 insertions(+), 29 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2022-05-18 18:44:52 | pgsql: Check column list length in XMLTABLE/JSON_TABLE alias |
Previous Message | Peter Eisentraut | 2022-05-18 16:21:16 | pgsql: Fix markup in synopsis |