From: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
---|---|
To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
Cc: | rightfold(at)gmail(dot)com, pgsql-docs(at)postgresql(dot)org |
Subject: | Re: gen_random_uuid security not explicit in documentation |
Date: | 2017-07-03 09:22:25 |
Message-ID: | 7aff5b9c-a7f2-96cd-0739-d2808cc3508a@iki.fi |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-hackers |
On 06/23/2017 04:23 AM, Michael Paquier wrote:
> On Fri, Jun 23, 2017 at 3:02 AM, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> wrote:
>> I'm inclined to change gen_random_uuid() to throw an error if the server is
>> built with --disable-strong-random, like gen_random_bytes() does. That way,
>> they would behave the same.
>
> No objections to do that. I guess you don't need a patch. As this is
> new to 10, I have added an open item.
Ok, pushed a fix to do that.
Thanks for bringing this up, Radek!
- Heikki
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2017-07-03 15:17:11 | Re: Documentation still mentioning SSLv2 and SSLv3 |
Previous Message | Arseny Sher | 2017-07-02 08:27:15 | Re: Synchronous logical replication? |
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Langote | 2017-07-03 09:32:24 | Re: Multi column range partition table |
Previous Message | Kyotaro HORIGUCHI | 2017-07-03 08:57:22 | Re: asynchronous execution |