Re: Move OpenSSL random under USE_OPENSSL_RANDOM

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Move OpenSSL random under USE_OPENSSL_RANDOM
Date: 2020-11-20 09:26:43
Message-ID: F567BA31-D2FF-45F8-8A6C-28AB3665630C@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 20 Nov 2020, at 03:31, Michael Paquier <michael(at)paquier(dot)xyz> wrote

> pg_strong_random.c needs a pgindent run, there are two inconsistent
> diffs. Looks fine except for those nits.

Agreed, this is the least complicated (and most readable) we can make this
file, especially if we add more providers. +1.

cheers ./daniel

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bharath Rupireddy 2020-11-20 09:34:57 Re: Skip ExecCheckRTPerms in CTAS with no data
Previous Message Bharath Rupireddy 2020-11-20 09:21:30 Re: Skip ExecCheckRTPerms in CTAS with no data