Re: [HACKERS] Re: protocol version negotiation (Re: Libpq PGRES_COPY_BOTH - version compatibility)

2017-10-30 Thread Badrul Chowdhury
;> <cr...@2ndquadrant.com>; Peter Eisentraut <pete...@gmx.net>; Magnus >> Hagander <mag...@hagander.net>; PostgreSQL-development > hack...@postgresql.org> >> Subject: Re: [HACKERS] Re: protocol version negotiation (Re: Libpq >> PGRES_COPY_BOTH - v

Re: [HACKERS] Re: protocol version negotiation (Re: Libpq PGRES_COPY_BOTH - version compatibility)

2017-10-27 Thread Robert Haas
On Thu, Oct 19, 2017 at 1:35 AM, Badrul Chowdhury wrote: > The new functionality is for sending 64bit ints. I think 32bits is sufficient > for the information we want to pass around in the protocol negotiation phase, > so I left this part unchanged. No, it isn't. That

Re: [HACKERS] Re: protocol version negotiation (Re: Libpq PGRES_COPY_BOTH - version compatibility)

2017-10-18 Thread Badrul Chowdhury
...@microsoft.com>; Craig Ringer >> <cr...@2ndquadrant.com>; Peter Eisentraut <pete...@gmx.net>; Magnus >> Hagander <mag...@hagander.net>; PostgreSQL-development > hack...@postgresql.org> >> Subject: Re: [HACKERS] Re: protocol version negotiation (Re: Libpq

Re: [HACKERS] Re: protocol version negotiation (Re: Libpq PGRES_COPY_BOTH - version compatibility)

2017-10-13 Thread Robert Haas
On Fri, Oct 6, 2017 at 5:07 PM, Badrul Chowdhury wrote: > I added a mechanism to fall back to v3.0 if the BE fails to start when FE > initiates a connection with v3.1 (with optional startup parameters). This > completely eliminates the need to backpatch older servers, ie

Re: [HACKERS] Re: protocol version negotiation (Re: Libpq PGRES_COPY_BOTH - version compatibility)

2017-10-06 Thread Badrul Chowdhury
>; Craig Ringer <cr...@2ndquadrant.com>; Peter Eisentraut <pete...@gmx.net>; Magnus Hagander <mag...@hagander.net>; PostgreSQL-development <pgsql-hackers@postgresql.org> Subject: Re: [HACKERS] Re: protocol version negotiation (Re: Libpq PGRES_COPY_BOTH - version comp

Re: [HACKERS] Re: protocol version negotiation (Re: Libpq PGRES_COPY_BOTH - version compatibility)

2017-10-04 Thread Badrul Chowdhury
.net>; Magnus Hagander <mag...@hagander.net>; PostgreSQL-development <pgsql-hackers@postgresql.org> Subject: Re: [HACKERS] Re: protocol version negotiation (Re: Libpq PGRES_COPY_BOTH - version compatibility) On Tue, Oct 3, 2017 at 9:46 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > B

Re: [HACKERS] Re: protocol version negotiation (Re: Libpq PGRES_COPY_BOTH - version compatibility)

2017-10-04 Thread Robert Haas
On Tue, Oct 3, 2017 at 9:46 PM, Tom Lane wrote: > Badrul Chowdhury writes: >> 1. Pgwire protocol v3.0 with negotiation is called v3.1. >> 2. There are 2 patches for the change: a BE-specific patch that will be >> backported and a FE-specific patch that

Re: [HACKERS] Re: protocol version negotiation (Re: Libpq PGRES_COPY_BOTH - version compatibility)

2017-10-03 Thread Tom Lane
Badrul Chowdhury writes: > 1. Pgwire protocol v3.0 with negotiation is called v3.1. > 2. There are 2 patches for the change: a BE-specific patch that will be > backported and a FE-specific patch that is only for pg10 and above. TBH, anything that presupposes a backported