Re: protocol version negotiation (Re: Libpq PGRES_COPY_BOTH - version compatibility)
Craig Ringer <craig@2ndquadrant.com>
From: Craig Ringer <craig@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Robert Haas <robertmhaas@gmail.com>, Peter Eisentraut <peter_e@gmx.net>, Magnus Hagander <magnus@hagander.net>,
PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2017-06-29T04:24:44Z
Lists: pgsql-hackers
On 29 June 2017 at 12:23, Craig Ringer <craig@2ndquadrant.com> wrote: > It does. But I don't see anywhere that extra round trips have been discussed. Ah, right, they're implied by having the server respond with some downversion message and ignore input until the client sends a new startup message. That'll only happen when a too-new client connects to an older server, but that's probably not an especially unusual case. -- Craig Ringer http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
Commits
-
Provide for forward compatibility with future minor protocol versions.
- aa3a78c3ddaf 9.3.21 landed
- 294136d42230 9.4.16 landed
- c703aa625899 9.5.11 landed
- 7c84bc0b3d70 9.6.7 landed
- 5b2a87707091 10.2 landed
- ae65f6066dc3 11.0 landed
-
Give nicer error message when connecting to a v10 server requiring SCRAM.
- 96d0f988b150 9.4.12 cited