Re: 2024-05-09 release announcement draft

2024-05-08 Thread Jonathan S. Katz
On 5/8/24 5:44 PM, David Rowley wrote: On Thu, 9 May 2024 at 04:17, Jonathan S. Katz wrote: * 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

Re: 2024-05-09 release announcement draft

2024-05-08 Thread David Rowley
On Thu, 9 May 2024 at 04:17, Jonathan S. Katz wrote: > * 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

Re: 2024-05-09 release announcement draft

2024-05-08 Thread Jonathan S. Katz
On 5/7/24 12:16 AM, Tom Lane wrote: David Rowley 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

Re: 2024-05-09 release announcement draft

2024-05-07 Thread Noah Misch
On Mon, May 06, 2024 at 11:09:24PM -0400, Jonathan S. Katz wrote: > * Avoid leaking a query result from > [`psql`](https://www.postgresql.org/docs/current/app-psql.html) > after the query is cancelled. I'd delete this item about a psql-lifespan memory leak, because (a) it's so minor and (b)

Re: 2024-05-09 release announcement draft

2024-05-06 Thread Tom Lane
David Rowley 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. regards, tom lane

Re: 2024-05-09 release announcement draft

2024-05-06 Thread David Rowley
On Tue, 7 May 2024 at 15:48, Tom Lane wrote: > > David Rowley writes: > > I know this is the same wording as Tom added in [1], I might just have > > failed to comprehend something, but if I strip out the links and try > > to make sense of "Fix INSERT from multiple VALUES rows into", I just > >

Re: 2024-05-09 release announcement draft

2024-05-06 Thread Tom Lane
David Rowley writes: > I know this is the same wording as Tom added in [1], I might just have > failed to comprehend something, but if I strip out the links and try > to make sense of "Fix INSERT from multiple VALUES rows into", I just > can't figure out how to parse it. I'm pretty sure it means

Re: 2024-05-09 release announcement draft

2024-05-06 Thread David Rowley
On Tue, 7 May 2024 at 15:09, Jonathan S. Katz wrote: > I opted for that; and it turned out the other fix was simple, so here's > an updated draft. Thanks > * Fix [`INSERT`](https://www.postgresql.org/docs/current/sql-insert.html) from > multiple

Re: 2024-05-09 release announcement draft

2024-05-06 Thread Jonathan S. Katz
On 5/6/24 11:05 PM, David Rowley wrote: On Tue, 7 May 2024 at 14:58, Jonathan S. Katz wrote: * Throw an error if an index is accessed while it is being reindexed. Based on this, I'd vote to just remove it from the release announcement. I'd prefer that over leaving the wording the way it

Re: 2024-05-09 release announcement draft

2024-05-06 Thread David Rowley
On Tue, 7 May 2024 at 14:58, Jonathan S. Katz wrote: > >> * Throw an error if an index is accessed while it is being reindexed. > > > > Based on this, I'd vote to just remove it from the release announcement. I'd prefer that over leaving the wording the way it is. Looking at the test case in

Re: 2024-05-09 release announcement draft

2024-05-06 Thread Tom Lane
"Jonathan S. Katz" writes: > On 5/6/24 5:08 PM, David Rowley wrote: >>> * Throw an error if an index is accessed while it is being reindexed. >>Maybe we should give more detail >> there so people don't think we made such a silly mistake. The release >> note version I think does have enough

Re: 2024-05-09 release announcement draft,2024-05-09 release announcement draft

2024-05-06 Thread Jonathan S. Katz
On 5/6/24 5:36 PM, Sutou Kouhei wrote: Hi, In <779790c7-45d7-4010-9305-c3f9e6a60...@postgresql.org>,<779790c7-45d7-4010-9305-c3f9e6a60...@postgresql.org> "2024-05-09 release announcement draft,2024-05-09 release announcement draft" on Mon, 6 May 2024 13:44:05 -0400

Re: 2024-05-09 release announcement draft

2024-05-06 Thread Jonathan S. Katz
On 5/6/24 5:08 PM, David Rowley wrote: On Tue, 7 May 2024 at 05:44, Jonathan S. Katz wrote: Please provide feedback no later (and preferably sooner) than 2024-05-09 12:00 UTC. Thanks for the draft. Here's some feedback. * Fix

Re: 2024-05-09 release announcement draft,2024-05-09 release announcement draft

2024-05-06 Thread Sutou Kouhei
Hi, In <779790c7-45d7-4010-9305-c3f9e6a60...@postgresql.org>,<779790c7-45d7-4010-9305-c3f9e6a60...@postgresql.org> "2024-05-09 release announcement draft,2024-05-09 release announcement draft" on Mon, 6 May 2024 13:44:05 -0400, "Jonathan S. Katz" wrote: &g

Re: 2024-05-09 release announcement draft

2024-05-06 Thread David Rowley
On Tue, 7 May 2024 at 05:44, Jonathan S. Katz wrote: > Please provide feedback no later (and preferably sooner) than 2024-05-09 > 12:00 UTC. Thanks for the draft. Here's some feedback. > * Fix [`INSERT`](https://www.postgresql.org/docs/current/sql-insert.html) from > multiple

Re: 2024-05-09 release announcement draft

2024-05-06 Thread Erik Rijkers
Op 5/6/24 om 19:44 schreef Jonathan S. Katz: Hi, Please find the draft of the 2024-05-09 release announcement. 'procedures that returns' should be 'procedures that return'

2024-05-09 release announcement draft

2024-05-06 Thread Jonathan S. Katz
Hi, Please find the draft of the 2024-05-09 release announcement. Please review for corrections and any omissions that should be called out as part of this release. Please provide feedback no later (and preferably sooner) than 2024-05-09 12:00 UTC. Thanks, Jonathan The PostgreSQL Global