Request a Demo
Home   >   mailing lists

Re: Adding OLD/NEW support to RETURNING - Mailing list pgsql-hackers

From Robert Treat
Subject Re: Adding OLD/NEW support to RETURNING
Date
Msg-id CAJSLCQ2X1REE9AjP7XY-fdOdaziNW_bZjsbOmoTiDkE23Vzs0g@mail.gmail.com
Whole thread Raw
In response to Adding OLD/NEW support to RETURNING  (Dean Rasheed <dean.a.rasheed@gmail.com>)
List pgsql-hackers
Tree view 
On Wed, Jun 25, 2025 at 7:42 AM Dean Rasheed <dean.a.rasheed@gmail.com> wrote:
>
> On Thu, 16 Jan 2025 at 15:28, Dean Rasheed <dean.a.rasheed@gmail.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

pgsql-hackers by date:

Previous
From: "Zhijie Hou (Fujitsu)"
Date:
Subject: RE: Conflict detection for update_deleted in logical replication
Next
From: Dilip Kumar
Date:
Subject: Re: pg_logical_slot_get_changes waits continously for a partial WAL record spanning across 2 pages