Re: pgsql: Use OpenSSL EVP API for symmetric encryption in pgcrypto.

From: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
To: Dave Page <dpage(at)postgresql(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-committers <pgsql-committers(at)postgresql(dot)org>
Subject: Re: pgsql: Use OpenSSL EVP API for symmetric encryption in pgcrypto.
Date: 2016-10-23 19:22:57
Message-ID: 8dd5efac-7157-0c6b-621d-d4a9ffb7eeee@iki.fi
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On 10/22/2016 07:11 PM, Tom Lane wrote:
> I wrote:
>> The only other Windows machines in the buildfarm that are building
>> with openssl are Andrew's bowerbird and frogmouth; they're both passing.
>> I wonder what openssl version is on those.
>
> What's the plan for getting the buildfarm back to green in the wake
> of this patch? If there isn't one, I'd like to request that the patch
> be reverted until such time as some effort can be put into it. Right
> now, these failures are preventing us from telling whether the recent
> postgres_fdw changes will pass everywhere.

Dave, what are we going to do about this? I cannot reproduce a similar
breakage on my system with OpenSSL 0.9.8 versions, and I don't have
access to the boxes themselves, so I'm pretty much stuck in trying to
debug the issue. And I wouldn't like to spend much time on that anyway,
given that the OpenSSL versions they use are ancient, and all other
buildfarm animals are happy.

Any chance you could update the OpenSSL versions on those systems, or
failing that, remove --with-openssl?

- Heikki

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2016-10-23 22:36:38 pgsql: Don't throw serialization errors for self-conflicts in INSERT ON
Previous Message Tom Lane 2016-10-23 19:02:38 pgsql: Avoid testing tuple visibility without buffer lock in RI_FKey_ch