On Wed, Nov 15, 2023 at 2:17 PM 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.
Hi hackers,
Indeed, I think it is a little confusing that when executing
EXPLAIN(ANALYZE), even though an update is actually occurring,
the commandtag of the update result is not returned.
However, the manual also describes the information that will be
affected when EXPLAIN (ANALYZE) is executed
> This creates a bug, not fixes one. It's intentional that "insert into a"
> is shown as returning zero rows, because that's what it did. If you'd
> written "insert ... returning", you'd have gotten a different result:
>
Maybe I didn't understand you correctly, but I didn't touch the number of
af
Damir Belyalov writes:
> I create a patch that outputs affected rows in EXPLAIN that occur by
> INSERT/UPDATE/DELETE.
> Despite the fact that commands in EXPLAIN ANALYZE query are executed as
> usual, EXPLAIN doesn't show outputting affected rows as in these commands.
> The patch fixes this proble
> On 6 Sep 2023, at 14:49, Damir Belyalov wrote
> The patch fixes this problem.
Given that EXPLAIN ANALYZE has worked like for a very long time, which problem
is it you have identified?
I'm also not convinced that the added "EXPLAIN" in the below plan is an
improvement in any way.
postgres=# e
