Re: Documenting MERGE INTO ONLY ...

From: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Nathan Bossart <nathandbossart(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Documenting MERGE INTO ONLY ...
Date: 2022-12-09 10:09:38
Message-ID: CAEZATCUXwyBmztv9MYpdU6st4KYCM1G+p2punb=Sxut2+iA1Kg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, 9 Dec 2022 at 10:02, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
>
> On 2022-Dec-08, Nathan Bossart wrote:
>
> > On Thu, Dec 08, 2022 at 03:26:52PM +0000, Dean Rasheed wrote:
> > > While testing MERGE, I noticed that it supports inheritance
> > > hierarchies and the ONLY keyword, but that isn't documented. Attached
> > > is a patch to merge.sgml, borrowing text from update.sgml and
> > > delete.sgml.
> >
> > LGTM.
>
> LGTM2.
>
> > I didn't see any tests for this in merge.sql or inherit.sql. Do you
> > think we should add some?
>
> Ouch! We should definitely have some.
>

Agreed. I just pushed this, with some additional tests.

Regards,
Dean

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Korotkov 2022-12-09 10:23:56 Re: Allow placeholders in ALTER ROLE w/o superuser
Previous Message Alvaro Herrera 2022-12-09 10:02:27 Re: Documenting MERGE INTO ONLY ...