| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, cary huang <hcary328(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Daniel Gustafsson <daniel(at)yesql(dot)se> |
| Subject: | Re: Setting min/max TLS protocol in clientside libpq |
| Date: | 2020-01-06 14:37:54 |
| Message-ID: | 31993.1578321474@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Magnus Hagander <magnus(at)hagander(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-01-06 15:15:19 | Re: pgsql: Add basic TAP tests for psql's tab-completion logic. |
| Previous Message | Magnus Hagander | 2020-01-06 13:59:14 | Re: Setting min/max TLS protocol in clientside libpq |