Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1o3xV2-0002OM-39 for pgsql-hackers@arkaria.postgresql.org; Wed, 22 Jun 2022 10:22:16 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1o3xUz-0002Yc-RR for pgsql-hackers@arkaria.postgresql.org; Wed, 22 Jun 2022 10:22:13 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1o3xUz-0002YT-0F for pgsql-hackers@lists.postgresql.org; Wed, 22 Jun 2022 10:22:13 +0000 Received: from wout4-smtp.messagingengine.com ([64.147.123.20]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1o3xUu-0006JF-Ls for pgsql-hackers@postgresql.org; Wed, 22 Jun 2022 10:22:11 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id A4B44320092A; Wed, 22 Jun 2022 06:22:05 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Wed, 22 Jun 2022 06:22:06 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1655893325; x= 1655979725; bh=M9mf3uhF5B5khKBQo9PRKwXVUr9lktOJpiecr7Eoy5E=; b=G HqDy0ZkjKeyzYIKj9xjRvm4V+LLxETJfrHk8sSg7VSjFDAVp6u/k6I8WEFbIrOIW Cg1gE25BJEcKmLd3U7syCHr9XiLBQcbCnjJD4UQ7O83URG3Yq7KpwfybP6vsrLa+ rDn6x3PfNvxQtBULhUCQsNxo9ccvgqBYyU9n5ohND6OvHOVFvYspzPNe4o4uaYTh LTOugEBJUJ0XhsZ/8L9TLqRO0PmqovuqPZpFkvKVkpXQfJl5kRV/+4t84hXH0oZH fr93mQFOSFn28m+e+xhy/k+dl5nRcYcyj6sxPrzTLeat0MvJ3qhj5Zma1KxYwarq hMO31zSxpK104aHsUwGrw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrudefhedgvdejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvvehfhfgjtgfgsehtjeertddtfeejnecuhfhrohhmpefrvght vghrucfgihhsvghnthhrrghuthcuoehpvghtvghrrdgvihhsvghnthhrrghuthesvghnth gvrhhprhhishgvuggsrdgtohhmqeenucggtffrrghtthgvrhhnpeehleffgeegudejteei hfelteduvdeifffhffdvjedvffegjeekudeludehudeifeenucevlhhushhtvghrufhiii gvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehpvghtvghrrdgvihhsvghnthhrrghu thesvghnthgvrhhprhhishgvuggsrdgtohhm X-ME-Proxy: Feedback-ID: i131946ab:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 22 Jun 2022 06:22:02 -0400 (EDT) Message-ID: Date: Wed, 22 Jun 2022 12:22:01 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.10.0 Subject: Re: Add header support to text format and matching feature Content-Language: en-US To: Michael Paquier Cc: Daniel Verite , Julien Rouhaud , Andrew Dunstan , Greg Stark , =?UTF-8?Q?R=c3=a9mi_Lapeyre?= , Zhihong Yu , David Steele , vignesh C , PostgreSQL-development References: <7ef90152-32e2-4f4b-9010-329a8dcc0c95@manitou-mail.org> <182b63dd-efa6-a108-4c28-fd5104518d01@enterprisedb.com> From: Peter Eisentraut In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 22.06.22 01:34, Michael Paquier wrote: > On Mon, Jun 20, 2022 at 09:03:23AM +0900, Michael Paquier wrote: >> On Thu, Jun 16, 2022 at 09:24:56AM +0200, Peter Eisentraut wrote: >>> I don't feel very strongly about this. It makes sense to stay consistent >>> with the existing COPY code. >> >> Yes, my previous argument is based on consistency with the >> surroundings. I am not saying that this could not be made better, it >> surely can, but I would recommend to tackle that in a separate patch, >> and apply that to more areas than this specific one. > > Peter, beta2 is planned for next week. Do you think that you would be > able to address this open item by the end of this week? If not, and I > have already looked at the proposed patch, I can jump in and help. The latest patch was posted by you, so I was deferring to you to commit it. Would you like me to do it?