Re: Setting min/max TLS protocol in clientside libpq - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Setting min/max TLS protocol in clientside libpq
Date
Msg-id 31993.1578321474@sss.pgh.pa.us
Whole thread Raw
In response to Re: Setting min/max TLS protocol in clientside libpq  (Magnus Hagander <magnus@hagander.net>)
Responses Re: Setting min/max TLS protocol in clientside libpq  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
Magnus Hagander <magnus@hagander.net> writes:
> Not having thought about it in much detail, but it's a fairly common
> scenario to have a much newer version of libpq (and the platform it's
> built on) than the server. E.g. a v12 libpq against a v9.6 postgres
> server is very common. For example, debian based systems will
> auto-upgrade your libpq, but not your server (for obvious reasons).
> And it's also quite common to upgrade platforms for the application
> much more frequently than the database server platform.

Yeah, there's a reason why we expect pg_dump and psql to function with
ancient server versions.  We shouldn't break this scenario with
careless rejiggering of libpq's connection defaults.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: Setting min/max TLS protocol in clientside libpq
Next
From: Tom Lane
Date:
Subject: Re: pgsql: Add basic TAP tests for psql's tab-completion logic.