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 1o1jsL-0003h1-FU for pgsql-hackers@arkaria.postgresql.org; Thu, 16 Jun 2022 07:25:09 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1o1jsI-0006Zk-H3 for pgsql-hackers@arkaria.postgresql.org; Thu, 16 Jun 2022 07:25:06 +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 1o1jsH-0006ZZ-Bb for pgsql-hackers@lists.postgresql.org; Thu, 16 Jun 2022 07:25:06 +0000 Received: from out5-smtp.messagingengine.com ([66.111.4.29]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1o1jsD-0003Lx-MQ for pgsql-hackers@postgresql.org; Thu, 16 Jun 2022 07:25:04 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 564F85C07BB; Thu, 16 Jun 2022 03:25:00 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Thu, 16 Jun 2022 03:25:00 -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=1655364300; x= 1655450700; bh=j3f6nz8KgKCehld22yYPLm5McUUhbH/qXDB9H0M79GE=; b=M e3JevK5+cEbLepRwdQBOqJXogLi5aqgAUvy5rD25LeIMTa3w7GrEd4tdBaELoCXi ejx/HJD6yQlmYLsCvCi/Z9uF+UQm90KQtctNTf6rWimTH6xyJgVc+c/ioHqOO1CH +ZtazyYZrLnbRAPFBo1S/venXXy8kvpvrKMLf1RtnvYvTMfCWm2ZOT/vfvHEuMDs PvYqPNw6Nfp9U6ayQ64I+gOkJfRpKq39cyNfzhU3gqIpZ9/B9kPufCpgBBv79ks5 H4F96D+rWbagW/eiylPgQ7unL/jhUm/ex+Z/onNweB2S5LPqnyB3iZzPVXcTFd0q si49iNAWKkMxS9655fzLA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedruddvvddguddujecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefkffggfgfuvfevfhfhjggtgfesthejredttdefjeenucfhrhhomheprfgv thgvrhcugfhishgvnhhtrhgruhhtuceophgvthgvrhdrvghishgvnhhtrhgruhhtsegvnh htvghrphhrihhsvggusgdrtghomheqnecuggftrfgrthhtvghrnhepheelffeggedujeet iefhleetuddvieffhfffvdejvdffgeejkeduleduheduieefnecuvehluhhsthgvrhfuih iivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepphgvthgvrhdrvghishgvnhhtrhgr uhhtsegvnhhtvghrphhrihhsvggusgdrtghomh X-ME-Proxy: Feedback-ID: i131946ab:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 16 Jun 2022 03:24:57 -0400 (EDT) Message-ID: <182b63dd-efa6-a108-4c28-fd5104518d01@enterprisedb.com> Date: Thu, 16 Jun 2022 09:24:56 +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: Daniel Verite , Julien Rouhaud Cc: Michael Paquier , 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> From: Peter Eisentraut In-Reply-To: <7ef90152-32e2-4f4b-9010-329a8dcc0c95@manitou-mail.org> 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 15.06.22 13:50, Daniel Verite wrote: > The other errors in the list above are more about the format itself, > with options that make sense only for one format. So the way we're > supposed to understand ERRCODE_FEATURE_NOT_SUPPORTED in these > other cases is that such format does not support such feature, > but without implying that it's a limitation. I don't feel very strongly about this. It makes sense to stay consistent with the existing COPY code.