From: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
---|---|
To: | David Rowley <dgrowleyml(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: 2023-08-10 release announcement draft |
Date: | 2023-08-08 02:03:44 |
Message-ID: | 8def4b82-abc8-6d9b-4b31-fea92f003766@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 8/7/23 9:53 PM, David Rowley wrote:
> On Tue, 8 Aug 2023 at 13:49, Jonathan S. Katz <jkatz(at)postgresql(dot)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
Attachment | Content-Type | Size |
---|---|---|
20230810updaterelease.md | text/plain | 9.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2023-08-08 02:15:41 | Cirrus-ci is lowering free CI cycles - what to do with cfbot, etc? |
Previous Message | 熊艳辉 | 2023-08-08 02:00:22 | 回复:Re: inconsistency between the VM page visibility status and the visibility status of the page |