| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Daniel Gustafsson <daniel(at)yesql(dot)se>, pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pgsql: Remove support for SSL compression |
| Date: | 2021-03-09 22:45:56 |
| Message-ID: | 2048261.1615329956@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Michael Paquier <michael(at)paquier(dot)xyz> writes:
> On Tue, Mar 09, 2021 at 10:58:21AM -0500, Tom Lane wrote:
>> In short, I think I'm a vote for reverting to the v13 behavior.
> The libpq part is a good point, as it could be annoying for people to
> get a changing behavior once the libpq version changes for anything
> using the older major version binaries once the newer libpq is out. I
> am still in favor of keeping the simplifications in the backend though
> as it simplifies some catalogs and PgBackendSSLStatus, and we know
> that SSL compression does not really matter these days.
I have no objection to the backend-side changes, since we can be sure
those won't affect people until they do a major-version upgrade to v14.
But the situation is squishier on the client side, and I don't really
see that pulling out libpq's support is buying us much.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2021-03-10 00:37:11 | pgsql: Revert changes for SSL compression in libpq |
| Previous Message | Michael Paquier | 2021-03-09 22:42:23 | Re: pgsql: Remove support for SSL compression |