Re: [PATCH] Add support for INSERT ... SET syntax

From: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Suraj Kharage <suraj(dot)kharage(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [PATCH] Add support for INSERT ... SET syntax
Date: 2026-03-30 15:49:12
Message-ID: 202603301544.utwvuj534m36@alvherre.pgsql
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2026-Mar-30, Andrew Dunstan wrote:

> Well, Suraj has kinda beaten me to it, but he didn't invent this syntax.
> Oracle did <https://oracle-base.com/articles/23/non-positional-insert-into-set-and-insert-into-by-name-clauses-23>
> and I believe there is a proposal to add it to the standard. (Unlike
> Suraj's, my WIP patch also supports the INSERT BY NAME variant.)

Hmm, I don't see any WIP patch from you -- are you talking about this
patch from July 2019?
https://postgr.es/m/CA+A-St+NntBh2EGu3a0xbVxJFzaeEOn=Vn_V84OuhM59_HKarQ@mail.gmail.com

Funnily enough, we have an even older proposal from 2016,
https://postgr.es/m/709e06c0-59c9-ccec-d216-21e38cb5ed61@joh.to

It seems this is quite a popular missing feature, as Marko's patch was
also asked about in February 2019:
https://postgr.es/m/e58dd487-7ed4-3f95-c63c-24200ed768be@berkvens.net

--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2026-03-30 16:11:17 Re: Adding locks statistics
Previous Message Sami Imseih 2026-03-30 15:32:41 Re: Add pg_stat_autovacuum_priority