Re: MERGE ... RETURNING

Vik Fearing <vik@postgresfriends.org>

From: Vik Fearing <vik@postgresfriends.org>

To: Jeff Davis <pgsql@j-davis.com>, Alvaro Herrera <alvherre@alvh.no-ip.org>, Dean Rasheed <dean.a.rasheed@gmail.com>

Cc: Isaac Morland <isaac.morland@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2023-07-12T01:47:24Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Add RETURNING support to MERGE.
- c649fa24a42b 17.0 landed
doc: Improve a couple of places in the MERGE docs.
- 97d4262683ac 17.0 landed
- d4c573d8e81e 16.3 landed
- a875743ff402 15.7 landed
doc: improve description of privileges for MERGE and update glossary.
- 4bc8f29088f8 17.0 landed
- 3b6728910ace 16.2 landed
- ff772853d02e 15.6 landed
Fix RLS policy usage in MERGE.
- c2e08b04c9e7 17.0 cited
Fix leak of LLVM "fatal-on-oom" section counter.
- 4f4d73466d71 17.0 cited
Implement outer-level aggregates to conform to the SQL spec, with
- e649796f128b 7.4.1 cited

On 7/12/23 02:43, Jeff Davis wrote:
> On Sun, 2023-01-22 at 19:58 +0100, Alvaro Herrera wrote:
>>
>> (We do have to keep our fingers
>> crossed that they will decide to use the same RETURNING syntax as we
>> do
>> in this patch, of course.)
> 
> Do we have a reason to think that they will accept something similar?

We have reason to think that they won't care at all.

There is no RETURNING clause in Standard SQL, and the way they would do 
this is:

     SELECT ...
     FROM OLD TABLE (
         MERGE ...
     ) AS m

The rules for that for MERGE are well defined.
-- 
Vik Fearing