Re: Removing support for COPY FROM STDIN in protocol version 2

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Removing support for COPY FROM STDIN in protocol version 2
Date: 2021-02-04 15:21:00
Message-ID: 4095287.1612452060@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2021-02-04 15:23:53 Re: Snapbuild woes followup
Previous Message Kohei KaiGai 2021-02-04 15:20:22 Re: Is MaxHeapAttributeNumber a reasonable restriction for foreign-tables?