Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sVnzh-00BisU-JZ for pgsql-hackers@arkaria.postgresql.org; Mon, 22 Jul 2024 08:02:05 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sVnzf-00G7O8-OR for pgsql-hackers@arkaria.postgresql.org; Mon, 22 Jul 2024 08:02:04 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sVnzf-00G7Jq-EA for pgsql-hackers@lists.postgresql.org; Mon, 22 Jul 2024 08:02:03 +0000 Received: from mail.clear-code.com ([2401:2500:102:3037:153:126:203:179]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sVnzY-000py9-Sb for pgsql-hackers@postgresql.org; Mon, 22 Jul 2024 08:02:03 +0000 Received: from localhost (unknown [IPv6:2404:7a80:89c1:1200:6af9:2266:1443:f149]) by mail.clear-code.com (Postfix) with ESMTPSA id DD643C0038; Mon, 22 Jul 2024 17:01:49 +0900 (JST) DKIM-Filter: OpenDKIM Filter v2.11.0 mail.clear-code.com DD643C0038 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=clear-code.com; s=default; t=1721635310; bh=8lzO2jPJMv0Lbf8aqIHj7+b1dplpz2TryKOikdYwmhE=; h=Date:To:Cc:Subject:From:In-Reply-To:References:From; b=mRY9tygmN8ulDyuXRqvho/uK62NteEaIdKEjr9jEcvu52jzW2H2NqrqQY1ksF+FJe UStNrWcRnshriM+jHD4T/YSPI2OaZbVy3ogpGZAzQd3unTKqScI82spOqAxDDn75nl GMqIQUrIwA+KwSFQStOwFHitZxe5l/BGj5QbfJYY= Date: Mon, 22 Jul 2024 17:01:49 +0900 (JST) Message-Id: <20240722.170149.849555541033173907.kou@clear-code.com> To: yoli@ebay.com Cc: andres@anarazel.de, michael@paquier.xyz, sawada.mshk@gmail.com, zhjwpku@gmail.com, andrew@dunslane.net, nathandbossart@gmail.com, pgsql-hackers@postgresql.org, tomas.vondra@enterprisedb.com Subject: Re: Make COPY format extendable: Extract COPY TO format implementations From: Sutou Kouhei In-Reply-To: <453D52D4-2AC5-49F6-928D-79F8A4C0850E@ebay.com> References: <20240410.171626.772425261553816667.kou@clear-code.com> <257d5573-07da-48c3-ac07-e047e7a65e99@enterprisedb.com> <453D52D4-2AC5-49F6-928D-79F8A4C0850E@ebay.com> X-Mailer: Mew version 6.8 on Emacs 29.4 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi Yong, Thanks for joining this thread! In <453D52D4-2AC5-49F6-928D-79F8A4C0850E@ebay.com> "Re: Make COPY format extendable: Extract COPY TO format implementations" on Mon, 22 Jul 2024 07:11:15 +0000, "Li, Yong" wrote: > My understanding is that the provided v17 patch aims to achieve the followings: > - Retain existing format implementations as built-in formats, and do not go through the new interface for them. > - Make sure that there is no sign of performance degradation. > - Refactoring the existing code to make it easier and possible to make copy handlers extensible. However, some of the infrastructure work that are required to make copy handler extensible are intentionally delayed for future patches. Some of the work were proposed as patches in earlier messages, but they were not explicitly referenced in recent messages. Right. Sorry for bothering you. As Tomas suggested, I should have prepared the current summary. My last e-mail summarized the current information: https://www.postgresql.org/message-id/flat/20240722.164540.889091645042390373.kou%40clear-code.com#0be14c4eeb041e70438ab7a423b728da It also shows that your understanding is right. Thanks, -- kou