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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Dave Page <dpage(at)postgresql(dot)org>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, pgsql-committers <pgsql-committers(at)postgresql(dot)org>
Subject: Re: pgsql: Use OpenSSL EVP API for symmetric encryption in pgcrypto.
Date: 2017-10-06 04:07:27
Message-ID: 14523.1507262847@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Dave Page <dpage(at)postgresql(dot)org> writes:
> On Mon, Oct 24, 2016 at 4:21 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>> On 10/24/2016 08:56 AM, Tom Lane wrote:
>>> I'd prefer the solution of disabling --with-openssl. If you just nuke
>>> those members, we never will find out whether the recent postgres_fdw
>>> changes pass on them. Besides, the point of the buildfarm has never
>>> been for all members to have the same configuration options.

>> Seems reasonable.

> OK, I think I got the perl stuff right - running test builds now.

Hey Dave, baiji has been failing the REL_10_STABLE branch since you
started running it there. I'm guessing you set it up to suppress
--with-openssl only for HEAD, and not for $branch ge 'REL_10' ...

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Paquier 2017-10-06 07:12:47 Re: [COMMITTERS] pgsql: Fix freezing of a dead HOT-updated tuple
Previous Message Tom Lane 2017-10-05 19:06:11 pgsql: Fix typo in README.