From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Random number generation, take two |
Date: | 2016-12-06 07:17:17 |
Message-ID: | CAB7nPqSz-RsKvZ2SswZDX_8uCy1cDTYjnp+60jMWHvbAi-wYoA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Dec 6, 2016 at 10:31 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I wrote:
>> Heikki Linnakangas <hlinnaka(at)iki(dot)fi> writes:
>>> Tom: I expect pademelon to fail at the configure step, complaining that
>>> "no source of strong random numbers was found". Let's wait for one
>>> cycle, to verify that it does fail like that. After that, can you add
>>> the --disable-strong-random flag to fix it, please?
>
>> Roger, I'll deal with that later today.
>
> Results seem to be as expected:
>
> http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=pademelon&dt=2016-12-05%2016%3A14%3A10
>
> http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=pademelon&dt=2016-12-05%2022%3A19%3A42
Nice to see. I'll send a rebased patch set for SCRAM soon now that we
know that things are fine here.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2016-12-06 07:38:56 | Re: Adding in docs the meaning of pg_stat_replication.sync_state |
Previous Message | Michael Paquier | 2016-12-06 07:15:07 | Re: pgcrypto compilation error due to stack-allocated EVP_CIPHER_CTX |