Re: 2024-05-09 release announcement draft - Mailing list pgsql-hackers

From Jonathan S. Katz
Subject Re: 2024-05-09 release announcement draft
Date
Msg-id 9d1bf0e0-bdcc-461b-8f76-4e14aa9c8caf@postgresql.org
Whole thread Raw
In response to Re: 2024-05-09 release announcement draft  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: 2024-05-09 release announcement draft
List pgsql-hackers
On 5/7/24 12:16 AM, Tom Lane wrote:
> David Rowley <dgrowleyml@gmail.com> writes:
>> Why not "Fix INSERT with multi-row VALUES clauses ..."?
> 
> To my mind, the VALUES clause is the data source for INSERT,
> so "from" seems appropriate.  I'm not going to argue hard
> about it.

OK, so I've read through this a few times and have sufficiently confused 
myself. So, how about this:

* Fix how 
[`INSERT`](https://www.postgresql.org/docs/current/sql-insert.html) 
handles multiple 
[`VALUES`](https://www.postgresql.org/docs/current/sql-values.html) rows 
into a target column that is a domain over an array or composite type.

Thanks,

Jonathan

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Fix for recursive plpython triggers
Next
From: "Imseih (AWS), Sami"
Date:
Subject: Re: New GUC autovacuum_max_threshold ?