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

From: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Removing support for COPY FROM STDIN in protocol version 2
Date: 2021-02-03 16:47:05
Message-ID: f69a7e6b-66f6-cbab-a414-ecc5c2127208@iki.fi
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 03/02/2021 18:29, Tom Lane wrote:
> Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
>> On 2021-Feb-03, Tom Lane wrote:
>>> I have a vague recollection that JDBC users still like to use
>>> protocol 2 for some reason --- is that out of date?
>
>> [ yes, since 2016 ]
>
> Then let's kill it dead, server and libpq both.

Ok, works for me. I'll prepare a larger patch to do that.

Since we're on a removal-spree, it'd also be nice to get rid of the
"fast-path" function call interface, PQfn(). However, libpq is using it
internally in the lo_*() functions, so if we remove it from the server,
lo_*() will stop working with old libpq versions. It would be good to
change those functions now to use PQexecParams() instead, so that we
could remove the fast-path server support in the future.

- Heikki

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Asif Rehman 2021-02-03 17:32:19 Re: Extensions not dumped when --schema is used
Previous Message Tom Lane 2021-02-03 16:29:37 Re: Removing support for COPY FROM STDIN in protocol version 2