Re: Move OpenSSL random under USE_OPENSSL_RANDOM
Magnus Hagander <magnus@hagander.net>
From: Magnus Hagander <magnus@hagander.net>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: Michael Paquier <michael@paquier.xyz>, Postgres hackers <pgsql-hackers@lists.postgresql.org>
Date: 2020-11-06T12:31:44Z
Lists: pgsql-hackers
On Fri, Nov 6, 2020 at 12:08 PM Daniel Gustafsson <daniel@yesql.se> wrote: > > > On 6 Nov 2020, at 00:36, Michael Paquier <michael@paquier.xyz> wrote: > > > I still don't see the point of this extra complexity, as > > USE_OPENSSL_RANDOM implies USE_OPENSSL, > > As long as we're sure that we'll remember to fix this when that assumption no > longer holds (intentional or unintentional) then it's fine to skip and instead > be defensive in documentation rather than code. I think the defensive-in-code instead of defensive-in-docs is a really strong argument, so I have pushed it as such. -- Magnus Hagander Me: https://www.hagander.net/ Work: https://www.redpill-linpro.com/
Commits
-
Remove ability to independently select random number generator
- 16f96c74d48e 14.0 landed
-
Add pg_strong_random_init function to initialize random number generator
- 5ee180a39470 14.0 landed