Re: Output affected rows in EXPLAIN

From: John Naylor <johncnaylorls(at)gmail(dot)com>
To: kuroda(dot)keisuke(at)nttcom(dot)co(dot)jp
Cc: Damir Belyalov <dam(dot)bel07(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, a(dot)lepikhov(at)postgrespro(dot)ru, Daniel Gustafsson <dgustafsson(at)postgresql(dot)org>
Subject: Re: Output affected rows in EXPLAIN
Date: 2023-11-22 10:07:47
Message-ID: CANWCAZZowoT67WqBp-9+wRzpvCEii-TwzN4JfsN9sQ6TJjoFPA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Nov 15, 2023 at 2:17 PM <kuroda(dot)keisuke(at)nttcom(dot)co(dot)jp> wrote:
>
> We can check the number of updated rows from execute plan,
> I think there is no need to return the command tag
> when EXPLAIN(ANALYZE) is executed by default.

Given that several people have voiced an opinion against this patch,
I'm marking it rejected.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii.Yuki@df.MitsubishiElectric.co.jp 2023-11-22 10:16:16 RE: Partial aggregates pushdown
Previous Message Cédric Villemain 2023-11-22 10:04:59 Re: Extension Enhancement: Buffer Invalidation in pg_buffercache