Re: Incorrect command tag row count for MERGE with a cross-partition update - Mailing list pgsql-hackers

From Dean Rasheed
Subject Re: Incorrect command tag row count for MERGE with a cross-partition update
Date
Msg-id CAEZATCWTTrGAgTfM_tNoGocnEKkYZT8dEic+Ewf_Ki76YCZ76w@mail.gmail.com
Whole thread Raw
In response to Re: Incorrect command tag row count for MERGE with a cross-partition update  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-hackers
On Tue, 21 Feb 2023 at 09:34, Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
>
> > I think the best fix is to have ExecMergeMatched() pass canSetTag =
> > false to ExecUpdateAct(), so that ExecMergeMatched() takes
> > responsibility for updating estate->es_processed in all cases.
>
> Sounds sensible.
>

I decided it was also probably worth having a regression test covering
this, since it would be quite easy to break if the code is ever
refactored.

Pushed and back-patched.

Regards,
Dean



pgsql-hackers by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: Reducing connection overhead in pg_upgrade compat check phase
Next
From: John Naylor
Date:
Subject: Re: [PoC] Improve dead tuple storage for lazy vacuum