Horton

Re: 2023-08-10 release announcement draft

Jonathan S. Katz <jkatz@postgresql.org>

View thread
From: "Jonathan S. Katz" <jkatz@postgresql.org>
To: David Rowley <dgrowleyml@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2023-08-08T02:03:44Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Release notes for 15.4, 14.9, 13.12, 12.16, 11.21.

Attachments

On 8/7/23 9:53 PM, David Rowley wrote:
> On Tue, 8 Aug 2023 at 13:49, Jonathan S. Katz <jkatz@postgresql.org> wrote:
>>
>> On 8/7/23 9:45 PM, David Rowley wrote:
>>
>>>> * Fix a performance regression when running concurrent
>>>> [`COPY`](https://www.postgresql.org/docs/16/sql-copy.html) statements on a
>>>> single table.
>>>
>>> I think this is still outstanding. A bit of work has been done for the
>>> int parsing regression but it seems there's still a performance
>>> regression when running multiple COPYs on the same table, per [1].
>>
>> Hm, the open item was closed[1] -- was that premature, or is this a new
>> issue (have not yet read the thread you referenced)?
> 
> I closed it thinking that enough had been done to resolve the
> performance regression. In the linked thread, Sawadasan shows that
> that's not the case. So, yes, premature.  I've reverted the change to
> the open items list now.

Got it. I reverted it as well from the release announcement. Reattaching 
with the clean copy.

(Aside: I'm super excited for this PG16 improvement + fixed regression, 
as lately I've had to do some bulk imports on a single table that could 
really benefit from this :)

Jonathan