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 1l7Kac-0004LB-4E for pgsql-hackers@arkaria.postgresql.org; Wed, 03 Feb 2021 16:01:10 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1l7Kab-0007v0-0c for pgsql-hackers@arkaria.postgresql.org; Wed, 03 Feb 2021 16:01:09 +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 1l7Kaa-0007uq-QJ for pgsql-hackers@lists.postgresql.org; Wed, 03 Feb 2021 16:01:08 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l7KaW-00033d-U7 for pgsql-hackers@postgresql.org; Wed, 03 Feb 2021 16:01:07 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 113G0qWf3908080; Wed, 3 Feb 2021 11:00:53 -0500 From: Tom Lane To: Heikki Linnakangas cc: pgsql-hackers Subject: Re: Removing support for COPY FROM STDIN in protocol version 2 In-reply-to: <9ec25819-0a8a-d51a-17dc-4150bb3cca3b@iki.fi> References: <9ec25819-0a8a-d51a-17dc-4150bb3cca3b@iki.fi> Comments: In-reply-to Heikki Linnakangas message dated "Wed, 03 Feb 2021 17:43:47 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3908078.1612368052.1@sss.pgh.pa.us> Date: Wed, 03 Feb 2021 11:00:52 -0500 Message-ID: <3908079.1612368052@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Heikki Linnakangas writes: > I propose that we remove server support for COPY FROM STDIN with > protocol version 2, per attached patch. Even if we could still support > it, it would be a very rarely used and tested codepath, prone to bugs. > Perhaps we could remove support for the old protocol altogether, but I'm > not proposing that we go that far just yet. I'm not really on board with half-baked removal of protocol 2. If we're going to kill it we should just kill it altogether. (The argument that it's untested surely applies to the rest of the P2 code as well.) I have a vague recollection that JDBC users still like to use protocol 2 for some reason --- is that out of date? regards, tom lane