Re: Setting min/max TLS protocol in clientside libpq
Michael Paquier <[email protected]>
| Newsgroups | gmane.comp.db.postgresql.devel.general |
|---|---|
| Message-ID | <[email protected]> |
On Mon, Jan 06, 2020 at 09:37:54AM -0500, Tom Lane wrote: > Magnus Hagander <[email protected]> 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. Good points. Let's not do that then. -- Michael
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAl4T1fwACgkQnvQgOdby QH1BXA//fM6nC72Oil5IM50omzw5XNwslhjVQGb7XKiGlihvwWWHQG9ULpSNMZJQ NJn/YUaEJixhpxslB1OBTRmGwFRa9t6wyftXtsRKlfHfSU2AyLHHf2ZLqIedJTe+ +8cvDoNmIaDrqeR7adi0r4bgHUXBjnoZCiaOfxra5I+9RbKnqzptdancz2FY+uwL 1ghlOl8KtxybALVb+RmP+oLQa5qWx40kGAV4xKM90e4RzV6Iap0Q4B5NC3vfcKi9 488SVD+4ELk0+w8bK3evZwpVH0nxsHua7VP//41zS9fXM675xEQ/Bl7UF58fvHUn NionZQrcPmqR8jQO+bCHK8dOlcqPsN5pvJTTdYcFgNSy5Y27vDmyv39PnPHqwWGD ghmR7kj/zC1wDyy5JkDokOqzaEdTa2jL1Ncl4Ps5+RZbAEYIlY5S1Sj/v9cgP603 Ux1kZWbAuH9K6lom84HMy8HVlr6qReI+D0Nm4TIosqFu//8DBCUKbxWPYokSTibd jPkULK47LV2JJajxuTZFM5AAZl8GDSgcM3aRBMsR8SxUHmOnI8vLK+EXyul9xitz 3mRMLItl5kdnvsTTZPOdmM+QnTljmyLA1sWO8086t4dFtkQw2L6hbkoIj2azRcWe x+rtqIWavOgCSyznuuyAVXl5w33BcFWRAS7JqwCHbV9o3h98sFI= =ExBS -----END PGP SIGNATURE-----