Re: Adding OLD/NEW support to RETURNING

From: Robert Treat <rob(at)xzilla(dot)net>
To: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>
Cc: jian he <jian(dot)universality(at)gmail(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Tomas Vondra <tomas(at)vondra(dot)me>
Subject: Re: Adding OLD/NEW support to RETURNING
Date: 2025-06-26 03:04:37
Message-ID: CAJSLCQ2X1REE9AjP7XY-fdOdaziNW_bZjsbOmoTiDkE23Vzs0g@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jun 25, 2025 at 7:42 AM Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> wrote:
>
> On Thu, 16 Jan 2025 at 15:28, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> wrote:
> >
> > I went over this again in detail and didn't find any problems, so I
> > have committed it. Thanks for all the review comments.
> >
>
> Looking at the doc pages for UPDATE and MERGE, I realise that I missed
> a paragraph in the "Description" section that needs updating.
>
> Patch attached.

At first look this seems right, modulo some typos

+ the old values of the target table's columns are used, but is it also
+ possible to explicity request old and new values. The syntax of the

should be "but it is also" and "explicitly".

Robert Treat
https://xzilla.net

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dilip Kumar 2025-06-26 03:18:32 Re: pg_logical_slot_get_changes waits continously for a partial WAL record spanning across 2 pages
Previous Message Zhijie Hou (Fujitsu) 2025-06-26 03:02:01 RE: Conflict detection for update_deleted in logical replication