pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Sutou Kouhei <kou@clear-code.com>
To: andres@anarazel.de
Cc: robertmhaas@gmail.com
Cc: laurenz.albe@cybertec.at
Cc: tgl@sss.pgh.pa.us
Cc: jack@jncsoftware.com
Cc: david@fetter.org
Cc: jeff.janes@gmail.com
Cc: pgsql-hackers@postgresql.org
Subject: Re: Why is pq_begintypsend so slow?
Date: Thu, 22 Feb 2024 15:40:55 +0900 (JST)
Message-ID: <20240222.154055.1131795475268328752.kou@clear-code.com> (raw)
In-Reply-To: <20240219195351.5vy7cdl3wxia66kg@awork3.anarazel.de>
References: <20240218200906.zvihkrs46yl2juzf@awork3.anarazel.de>
	<20240219.100252.1610549091537921652.kou@clear-code.com>
	<20240219195351.5vy7cdl3wxia66kg@awork3.anarazel.de>

Hi,

In <20240219195351.5vy7cdl3wxia66kg@awork3.anarazel.de>
  "Re: Why is pq_begintypsend so slow?" on Mon, 19 Feb 2024 11:53:51 -0800,
  Andres Freund <andres@anarazel.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





view thread (29+ messages)

Message-ID: <20240222.154055.1131795475268328752.kou@clear-code.com>
Permalink:  ../20240222.154055.1131795475268328752.kou@clear-code.com/
Also on:    postgresql.org/message-id/20240222.154055.1131795475268328752.kou@clear-code.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: kou@clear-code.com, andres@anarazel.de, robertmhaas@gmail.com, laurenz.albe@cybertec.at, tgl@sss.pgh.pa.us, jack@jncsoftware.com, david@fetter.org, jeff.janes@gmail.com
  Subject: Re: Why is pq_begintypsend so slow?
  In-Reply-To: <20240222.154055.1131795475268328752.kou@clear-code.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox