| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | 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 14:56:12 |
| Message-ID: | 2009392.1774882572@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> On Monday, March 30, 2026, Suraj Kharage <suraj(dot)kharage(at)enterprisedb(dot)com>
> wrote:
>> I would like to propose adding support for an alternative INSERT syntax
>> that uses named column assignments via a SET clause. This provides a more
>> convenient and readable way to write inserts, particularly when only
>> specific columns need values.
> -1 for inventing our own full variant of insert command syntax.
This has been discussed before, no? I don't recall exactly why
we didn't adopt the earlier proposal(s), but some digging in the
mailing list archives should be fruitful.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ants Aasma | 2026-03-30 15:00:59 | Re: Proposal for enabling auto-vectorization for checksum calculations |
| Previous Message | Tom Lane | 2026-03-30 14:54:11 | Re: Thread-safe getopt() |