| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Luca Ferrari <fluca1978(at)gmail(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: MERGE output doubt |
| Date: | 2022-11-17 17:57:33 |
| Message-ID: | 20221117175733.yd3g5usesadm5sg3@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zheng Li | 2022-11-17 19:01:50 | Re: Support logical replication of DDLs |
| Previous Message | Вадим Самохин | 2022-11-17 17:42:21 | Re: Postgresql 11.3 doesn't use gist index on polygon column |