| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Badrul Chowdhury <bachow(at)microsoft(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Satyanarayana Narlapuram <Satyanarayana(dot)Narlapuram(at)microsoft(dot)com>, Craig Ringer <craig(at)2ndquadrant(dot)com>, "Peter Eisentraut" <peter_e(at)gmx(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Re: protocol version negotiation (Re: Libpq PGRES_COPY_BOTH - version compatibility) |
| Date: | 2017-10-04 01:46:26 |
| Message-ID: | 2511.1507081586@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Badrul Chowdhury <bachow(at)microsoft(dot)com> 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 change in the backend is
broken by definition. We expect libpq to be able to connect to older
servers, and that has to include servers that didn't get this memo.
It would be all right for libpq to make a second connection attempt
if its first one fails, as we did in the 2.0 -> 3.0 change.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Wong, Yi Wen | 2017-10-04 03:43:00 | Re: [COMMITTERS] pgsql: Fix freezing of a dead HOT-updated tuple |
| Previous Message | Tom Lane | 2017-10-04 01:41:27 | Re: Warnings in objectaddress.c |