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: PostgreSQL 17 Beta 1 release announcement draft |
Date: | 2024-05-20 11:44:11 |
Message-ID: | 0e4397e6-9e47-4e10-aeee-0bb6f39979e5@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 5/19/24 7:24 PM, David Rowley wrote:
> On Mon, 20 May 2024 at 09:35, Jonathan S. Katz <jkatz(at)postgresql(dot)org> wrote:
>> Thanks for all the feedback to date. Please see the next revision.
>> Again, please provide feedback no later than 2024-05-22 18:00 UTC.
>
> Thanks for the updates.
>
>> [`COPY`](https://www.postgresql.org/docs/17/sql-copy.html) is used to efficiently bulk load data into PostgreSQL, and with PostgreSQL 17 shows a 2x performance improvement when loading large rows.
>
> The 2x thing mentioned by Jelte is for COPY TO rather than COPY FROM.
> So I think "exporting" or "sending large rows to the client" rather
> than "loading".
Thanks for the clarification - I've edited it as such. That also brings
up a good point to highlight that COPY is not just for loading (since my
bias is to do loads these days :) Now it reads:
[`COPY`](https://www.postgresql.org/docs/17/sql-copy.html) is used to
efficiently bulk load and export data from PostgreSQL, and now with
PostgreSQL 17 you may see up to a 2x performance improvement when
exporting large rows.
> There's also a stray "with" in that sentence.
Thanks, fixed.
Jonathan
From | Date | Subject | |
---|---|---|---|
Next Message | Jonathan S. Katz | 2024-05-20 11:47:54 | Re: PostgreSQL 17 Beta 1 release announcement draft |
Previous Message | Alvaro Herrera | 2024-05-20 11:41:13 | Re: commitfest.postgresql.org is no longer fit for purpose |