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 1l7gS5-0008Dk-UT for pgsql-hackers@arkaria.postgresql.org; Thu, 04 Feb 2021 15:21:49 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1l7gRZ-0006Kf-0z for pgsql-hackers@arkaria.postgresql.org; Thu, 04 Feb 2021 15:21:17 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l7gRY-0006KS-Qs for pgsql-hackers@lists.postgresql.org; Thu, 04 Feb 2021 15:21:16 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l7gRW-0007iP-NU for pgsql-hackers@postgresql.org; Thu, 04 Feb 2021 15:21:16 +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 114FL0PQ4095288; Thu, 4 Feb 2021 10:21:00 -0500 From: Tom Lane To: Alvaro Herrera cc: Heikki Linnakangas , Michael Paquier , pgsql-hackers Subject: Re: Removing support for COPY FROM STDIN in protocol version 2 In-reply-to: <20210204150542.GA4802@alvherre.pgsql> References: <20210204150542.GA4802@alvherre.pgsql> Comments: In-reply-to Alvaro Herrera message dated "Thu, 04 Feb 2021 12:05:42 -0300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <4095286.1612452060.1@sss.pgh.pa.us> Date: Thu, 04 Feb 2021 10:21:00 -0500 Message-ID: <4095287.1612452060@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Alvaro Herrera writes: > On 2021-Feb-04, Heikki Linnakangas wrote: >> Ok, here we go. > Are you going to bump the .so version for this? I think that should be > done, since some functions disappear and there are struct changes. It > is curious, though, to see that exports.txt needs no changes. Uh, what? There should be no externally visible ABI changes in libpq (he says without having read the patch). If there's a need for a library major version bump, that'd be sufficient reason not to do this IMO. regards, tom lane