Re: Move OpenSSL random under USE_OPENSSL_RANDOM

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Move OpenSSL random under USE_OPENSSL_RANDOM
Date: 2020-11-19 03:34:33
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Wed, Nov 18, 2020 at 10:43:35AM +0100, Daniel Gustafsson wrote:
> While it does simplify, I'm just not a fan of the strict ordering
> which is required without the labels even implying it. But that might just be
> my personal preference.

I just looked at that, and the attached seems more intuitive to me.
There is more code removed, but not that much either.

Attachment Content-Type Size
v3-0001-Remove-ability-to-choose-randomness-source.patch text/x-diff 10.9 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2020-11-19 03:39:18 Re: "as quickly as possible" (was: remove spurious CREATE INDEX CONCURRENTLY wait)
Previous Message Amit Kapila 2020-11-19 03:22:44 Re: POC: Cleaning up orphaned files using undo logs