| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
| 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 04:16:56 |
| Message-ID: | 20230525041656.25llpb2atpge4j4w@awork3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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...
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2023-05-25 05:57:25 | Re: PG 16 draft release notes ready |
| Previous Message | Jonathan S. Katz | 2023-05-25 03:32:02 | Re: PostgreSQL 16 Beta 1 release announcement draft |