On Tue, Oct 3, 2017 at 9:46 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Badrul Chowdhury <bac...@microsoft.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.
Hmm, that's another approach, but I prefer the one advocated by Tom Lane. https://www.postgresql.org/message-id/30788.1498672...@sss.pgh.pa.us https://www.postgresql.org/message-id/24357.1498703265%40sss.pgh.pa.us -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (firstname.lastname@example.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers