Horton

Re: Adding OLD/NEW support to RETURNING

Robert Treat <rob@xzilla.net>

View thread
From: Robert Treat <rob@xzilla.net>
To: Dean Rasheed <dean.a.rasheed@gmail.com>
Cc: jian he <jian.universality@gmail.com>, Jeff Davis <pgsql@j-davis.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Tomas Vondra <tomas@vondra.me>
Date: 2025-06-26T03:04:37Z
Lists: pgsql-hackers 
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