Re: pgsql: Set libpq sslcompression to off by default

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Set libpq sslcompression to off by default
Date: 2018-03-21 00:42:18
Message-ID: 79CD9CA1-E394-4C1F-940F-78A9D00DAE59@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

> On 20 Mar 2018, at 22:00, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
>
> On 3/20/18 04:03, Daniel Gustafsson wrote:
>> If we test for SSL_clear_options(), and use the sk_SSL_COMP_zero() where not
>> available, we should be able to keep backwards compatibility with older OpenSSL
>> revisions even if the distros have patched them AFAICT. Unless you’re already
>> working on it I can take a stab at it.
>
> I don't think we need to go out of our way to deal with such old
> versions (> 8 years AFAICT), especially since we have no way to test it.

Fair enough, makes sense.

cheers ./daniel

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Andres Freund 2018-03-21 00:47:12 pgsql: Handle EEOP_FUNCEXPR_[STRICT_]FUSAGE out of line.
Previous Message Andres Freund 2018-03-21 00:29:47 pgsql: Add configure infrastructure (--with-llvm) to enable LLVM suppor