| From: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
|---|---|
| To: | Ajin Cherian <itsajin(at)gmail(dot)com> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Add support for COPY TO in tablesync for partitioned tables. |
| Date: | 2025-11-12 21:49:22 |
| Message-ID: | CAD21AoDVuFensxY8D9fnkaK2_igbKS9LxY8J2rTykns1CJ+0KA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Nov 10, 2025 at 7:37 PM Ajin Cherian <itsajin(at)gmail(dot)com> wrote:
>
> On Tue, Nov 11, 2025 at 2:19 PM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> >
> > In the commit message, you mentioned: "Performance tests show it's
> > faster than the COPY (SELECT ...) TO variant as it avoids the
> > overheads of query processing and sending results to the COPY TO
> > command.". Can you share the performance data to substantiate this
> > point?
> >
>
> This was based on the tests done in the original thread [1] and [2]
Thank you for working on this item. I think it's a good follow-up
patch for commit 4bea91f.
Have you conducted any performance tests with logical replication
setup? I've measured normal COPY TO cases but I think it would be
worth checking how much the performance increase we can see in logical
replication setup too.
Regards,
--
Masahiko Sawada
Amazon Web Services: https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sami Imseih | 2025-11-12 22:10:22 | Re: another autovacuum scheduling thread |
| Previous Message | Jacob Champion | 2025-11-12 21:47:58 | Re: Early December Commitfest app release |