| From: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, David Rowley <dgrowleyml(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: 2024-05-09 release announcement draft |
| Date: | 2024-05-08 16:17:13 |
| Message-ID: | 9d1bf0e0-bdcc-461b-8f76-4e14aa9c8caf@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 5/7/24 12:16 AM, Tom Lane wrote:
> David Rowley <dgrowleyml(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Imseih (AWS), Sami | 2024-05-08 17:30:44 | Re: New GUC autovacuum_max_threshold ? |
| Previous Message | Tom Lane | 2024-05-08 15:51:17 | Re: Fix for recursive plpython triggers |