| From: | "Ryohei Takahashi (Fujitsu)" <r(dot)takahashi_2(at)fujitsu(dot)com> |
|---|---|
| To: | 'Vladlen Popolitov' <v(dot)popolitov(at)postgrespro(dot)ru> |
| Cc: | 'Robert Haas' <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | RE: COPY performance on Windows |
| Date: | 2025-01-14 06:50:17 |
| Message-ID: | TY3PR01MB118912C0D2D55359C7AD3E73582182@TY3PR01MB11891.jpnprd01.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
I did more investigation on the COPY performance on Windows.
By using community distributed binaries, the COPY performance of PG16.6 and PG17.0 is worse than PG16.4.
However, by using the binaries build by myself, there are no difference.
So, it is not the problem about the source code after PG16.4.
On the other hand, I noticed that 82a4edabd2 is degrading COPY performance on Windows.
I will write the detail in the next e-mail.
Regards,
Ryohei Takahashi
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shubham Khanna | 2025-01-14 06:54:19 | Re: Log a warning in pg_createsubscriber for max_slot_wal_keep_size |
| Previous Message | Michael Paquier | 2025-01-14 06:28:17 | Re: Possible integer overflow in bringetbitmap() |