From: | Dave Page <dpage(at)postgresql(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
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 08:42:13 |
Message-ID: | CA+OCxowOeyiK+N-Dy4geJhjsHz_5e2ANztu68vzcXn4kokvS5g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
On Fri, Oct 6, 2017 at 5:07 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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' ...
>
Argh, yes. Should be fixed now.
Thanks.
--
Dave Page
PostgreSQL Core Team
http://www.postgresql.org/
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2017-10-06 10:57:18 | Re: [COMMITTERS] pgsql: Fix freezing of a dead HOT-updated tuple |
Previous Message | Noah Misch | 2017-10-06 07:30:55 | Re: pgsql: Remove ICU tests from default run |