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 01:49:26 |
Message-ID: | 07de16ad-449b-120e-3e8a-596fb022104b@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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)?
>> or an previous major version of PostgreSQL, you will need to use a strategy
>
> "a previous".
Thanks for the catch -- fixed locally.
Jonathan
[1]
https://wiki.postgresql.org/index.php?title=PostgreSQL_16_Open_Items#resolved_before_16beta3
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2023-08-08 01:53:30 | Re: 2023-08-10 release announcement draft |
Previous Message | David Rowley | 2023-08-08 01:45:13 | Re: 2023-08-10 release announcement draft |