From: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Erik Rijkers <er(at)xs4all(dot)nl>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Nathan Bossart <nathandbossart(at)gmail(dot)com> |
Subject: | Re: PostgreSQL 16 Beta 1 release announcement draft |
Date: | 2023-05-25 14:40:16 |
Message-ID: | da64d92f-3fc8-2cf7-6b41-81f931a0f2bd@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 5/25/23 12:16 AM, Andres Freund wrote:
> Hi,
>
> On 2023-05-24 23:30:58 -0400, Jonathan S. Katz wrote:
>>> Ah, OK, that's why I didn't grok it. I read through the first message
>>> in[1] and definitely agree it should be in the announcement. How about:
>>>
>>> "PostgreSQL 16 also shows up to a 300% improvement when concurrently
>>> loading data with `COPY`"
>>
>> I currently have it as the below in the release announcement. If it you send
>> any suggested updates, I can try to put them in before release:
>>
>> PostgreSQL 16 can also improve the performance of concurrent bulk loading of
>> data using [`COPY`](https://www.postgresql.org/docs/16/sql-copy.html) up to
>> a 300%.
>
> It also speeds up concurrent loading when not using COPY, just to a lesser
> degree. But I can't come up with a concise phrasing for that right now...
I left as is (in part because of a hurried morning), but we can improve
upon it for the GA.
Thanks,
Jonathan
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2023-05-25 14:41:14 | Re: memory leak in trigger handling (since PG12) |
Previous Message | Tom Lane | 2023-05-25 14:29:14 | Re: Wrong results due to missing quals |