| From: | Sutou Kouhei <kou(at)clear-code(dot)com> |
|---|---|
| To: | andres(at)anarazel(dot)de |
| Cc: | robertmhaas(at)gmail(dot)com, laurenz(dot)albe(at)cybertec(dot)at, tgl(at)sss(dot)pgh(dot)pa(dot)us, jack(at)jncsoftware(dot)com, david(at)fetter(dot)org, jeff(dot)janes(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Why is pq_begintypsend so slow? |
| Date: | 2024-02-22 06:40:55 |
| Message-ID: | 20240222.154055.1131795475268328752.kou@clear-code.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
In <20240219195351(dot)5vy7cdl3wxia66kg(at)awork3(dot)anarazel(dot)de>
"Re: Why is pq_begintypsend so slow?" on Mon, 19 Feb 2024 11:53:51 -0800,
Andres Freund <andres(at)anarazel(dot)de> wrote:
>> I don't have a strong opinion how to implement this
>> optimization as I said above. It seems that you like your
>> approach. So I withdraw [1]. Could you complete this
>> optimization? Can we proceed making COPY format extensible
>> without this optimization? It seems that it'll take a little
>> time to complete this optimization because your patch is
>> still WIP. And it seems that you can work on it after making
>> COPY format extensible.
>
> I don't think optimizing this aspect needs to block making copy extensible.
OK. I'll work on making copy extensible without this
optimization.
> I don't know how much time/energy I'll have to focus on this in the near
> term. I really just reposted this because the earlier patches were relevant
> for the discussion in another thread. If you want to pick the COPY part up,
> feel free.
OK. I may work on this after I complete making copy
extensible if you haven't completed this yet.
Thanks,
--
kou
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2024-02-22 06:44:16 | Re: Make COPY format extendable: Extract COPY TO format implementations |
| Previous Message | Richard Guo | 2024-02-22 06:35:41 | Re: POC: GROUP BY optimization |