From: Tom Lane <tgl@sss.pgh.pa.us>
To: James Stuart <slim2k@privatejuris.org>
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: UPDATE mentions the RETURNING * syntax but does not mention
 RETURNING * INTO ...
In-reply-to: <117a4e32-a7d3-543e-b936-467b488981d4@privatejuris.org>
References: <117a4e32-a7d3-543e-b936-467b488981d4@privatejuris.org>
Comments: In-reply-to James Stuart <slim2k@privatejuris.org>
	message dated "Mon, 04 Sep 2023 10:55:05 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1198350.1693861213.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Mon, 04 Sep 2023 17:00:13 -0400
Message-ID: <1198351.1693861213@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1198351.1693861213%40sss.pgh.pa.us>
Precedence: bulk

James Stuart <slim2k@privatejuris.org> writes:
> UPDATE mentions the RETURNING * syntax but does not mention RETURNING * =

> INTO ...

> https://www.postgresql.org/docs/15/sql-update.html

That's because there is no such thing so far as the core SQL parser is
concerned (so if you try it from, say, psql, it won't work).

There is such syntax in plpgsql, and that's where it's documented:

https://www.postgresql.org/docs/current/plpgsql-statements.html#PLPGSQL-ST=
ATEMENTS-SQL-ONEROW

			regards, tom lane