| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | backward compatibility of GSSENCRequest |
| Date: | 2019-08-23 10:09:26 |
| Message-ID: | a3fdc44e-21a1-7493-46c4-a1a76465bb9e@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
As of PostgreSQL, an appropriately built client will initiate TCP/IP
connections with these packets:
1. GSSENCRequest
2. SSLRequest
3. StartupMessage
Older servers will respond to the first one with:
FATAL: unsupported frontend protocol 1234.5680: server supports 2.0 to 3.0
libpq will then try to reconnect with SSLRequest. So this works out in
practice, but it will require two TCP/IP connections and leave these
messages in the log.
I think we should at least document this somehow in the release notes.
Also, third-party implementors of the server protocol should be made
aware of this, again probably via the release notes.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dmitry Dolgov | 2019-08-23 10:14:05 | Re: io_uring support |
| Previous Message | Michael Paquier | 2019-08-23 09:45:35 | Re: pg_checksums --help synopsis is quite long |