Re: openssl valgrind failures on skink are due to openssl issue

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: openssl valgrind failures on skink are due to openssl issue
Date: 2019-06-12 07:50:41
Message-ID: 20190612075041.GE1745@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jun 11, 2019 at 02:07:29PM -0700, Andres Freund wrote:
> On 2019-06-11 16:55:28 -0400, Tom Lane wrote:
>> Andres Freund <andres(at)anarazel(dot)de> writes:
>>> I can't think of a better way to fix skink for now than just disabling
>>> openssl for skink, until 1.1.1d is released.

Thanks for digging into the details of that! I was wondering if we
did something wrong on our side but the backtraces were weird.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message alex lock 2019-06-12 07:58:06 set parameter for all existing session
Previous Message Siarhei Siniak 2019-06-12 07:50:22 Re: GiST limits on contrib/cube with dimension > 100?