Re: MERGE output doubt - Mailing list pgsql-general

From Alvaro Herrera
Subject Re: MERGE output doubt
Date
Msg-id 20221117175733.yd3g5usesadm5sg3@alvherre.pgsql
Whole thread Raw
In response to Re: MERGE output doubt  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-general
On 2022-Nov-17, Alvaro Herrera wrote:

> On 2022-Oct-20, Luca Ferrari wrote:
> 
> > I was expecting an output tag like "MERGE 0" since both branches have
> > "do nothing", so no tuples should be updated at all on the target
> > table.
> 
> Hmm, yeah, it should report 0 tuples, according to the documentation.
> AFAICS this patch fixes it, will push shortly.

Pushed, thanks for reporting.

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/
"Someone said that it is at least an order of magnitude more work to do
production software than a prototype. I think he is wrong by at least
an order of magnitude."                              (Brian Kernighan)



pgsql-general by date:

Previous
From: Вадим Самохин
Date:
Subject: Re: Postgresql 11.3 doesn't use gist index on polygon column
Next
From: Bryn Llewellyn
Date:
Subject: Seeking practice recommendation: is there ever a use case to have two or more superusers?