From: | Sutou Kouhei <kou(at)clear-code(dot)com> |
---|---|
To: | zhjwpku(at)gmail(dot)com |
Cc: | sawada(dot)mshk(at)gmail(dot)com, michael(at)paquier(dot)xyz, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Make COPY format extendable: Extract COPY TO format implementations |
Date: | 2025-01-23 09:09:29 |
Message-ID: | 20250123.180929.1687845160025621890.kou@clear-code.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
In <CAEG8a3+-3fAmiwD5NmE7W4j5-=HLs2OEexQNW9-fB=j=mdxgDQ(at)mail(dot)gmail(dot)com>
"Re: Make COPY format extendable: Extract COPY TO format implementations" on Fri, 29 Nov 2024 10:15:04 +0800,
Junwang Zhao <zhjwpku(at)gmail(dot)com> wrote:
> This thread and [1] thread are kind of interleaved, I chose this thread
> to share the numbers because I think this feature should be committed
> first and then adapt the *copy to json* as a contrib module.
I agree with you.
> Committers on this thread seem worried about the performance
> drawback, so what I tried to do is that *if 2 is slightly worse than 1,
> but better than 3*, then we can commit 2 first, but I did not get
> the expected number.
Could you break down which patch in the v13 patch set[1]
affected? If we can find which change improves performance,
we can use the approach in this patch set too.
Thanks,
--
kou
From | Date | Subject | |
---|---|---|---|
Next Message | Sutou Kouhei | 2025-01-23 09:12:10 | Re: Make COPY format extendable: Extract COPY TO format implementations |
Previous Message | Frédéric Yhuel | 2025-01-23 09:00:27 | Re: doc: explain pgstatindex fragmentation |