Re: Doc updates for MERGE

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Doc updates for MERGE
Date: 2023-02-24 08:56:22
Message-ID: 20230224085622.tmlrb33lvaicgcon@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2023-Feb-24, Dean Rasheed wrote:

> Attached is a patch fixing a few doc omissions for MERGE.
>
> I don't think that it's necessary to update every place that could
> possibly apply to MERGE, but there are a few places where we give a
> list of commands that may be used in a particular context, and I think
> those should mention MERGE, if it applies.

Agreed. Your patch looks good to me.

I was confused for a bit about arch-dev.sgml talking about ModifyTable
when perform.sgml talks about Insert/Update et al; I thought at first
that one or the other was in error, so I checked. It turns out that
they are both correct, because arch-dev is talking about code-level
executor nodes while perform.sgml is talking about how it looks under
EXPLAIN. So, it all looks good.

I assume you're proposing to back-patch this.

--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
"La verdad no siempre es bonita, pero el hambre de ella sí"

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message gkokolatos 2023-02-24 09:21:32 Re: Add LZ4 compression in pg_dump
Previous Message Pavel Borisov 2023-02-24 08:42:45 Re: Should vacuum process config file reload more often