Re: 2024-05-09 release announcement draft
Jonathan S. Katz <jkatz@postgresql.org>
From: "Jonathan S. Katz" <jkatz@postgresql.org>
To: Tom Lane <tgl@sss.pgh.pa.us>, David Rowley <dgrowleyml@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2024-05-08T16:17:13Z
Lists: 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
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
First-draft release notes for 16.3.
- 7155cc4a60e7 16.3 cited