> On 20 Mar 2018, at 22:00, Peter Eisentraut
> 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 dis
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 o
> On 20 Mar 2018, at 05:15, Tom Lane wrote:
>
> Peter Eisentraut writes:
>> On 3/17/18 15:12, Daniel Gustafsson wrote:
>>> On 17 Mar 2018, at 17:47, Tom Lane wrote:
Buildfarm reports that SSL_clear_options isn't available everywhere.
>
>>> Per some reading of the documentation and various
Peter Eisentraut writes:
> On 3/17/18 15:12, Daniel Gustafsson wrote:
>> On 17 Mar 2018, at 17:47, Tom Lane wrote:
>>> Buildfarm reports that SSL_clear_options isn't available everywhere.
>> Per some reading of the documentation and various patchers it seems
>> SSL_clear_options() was introduced
On 3/17/18 15:12, Daniel Gustafsson wrote:
>> On 17 Mar 2018, at 17:47, Tom Lane wrote:
>>
>> Peter Eisentraut writes:
>>> Set libpq sslcompression to off by default
>>
>> Buildfarm reports that SSL_clear_options isn't available everywhere.
>
> Per some reading of the documentation and various p
> On 17 Mar 2018, at 17:47, Tom Lane wrote:
>
> Peter Eisentraut writes:
>> Set libpq sslcompression to off by default
>
> Buildfarm reports that SSL_clear_options isn't available everywhere.
Per some reading of the documentation and various patchers it seems
SSL_clear_options() was introduced
Peter Eisentraut writes:
> Set libpq sslcompression to off by default
Buildfarm reports that SSL_clear_options isn't available everywhere.
regards, tom lane
