Re: Support getrandom() for pg_strong_random() source

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
Cc: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org>, Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Support getrandom() for pg_strong_random() source
Date: 2025-07-28 16:14:20
Message-ID: 06C064B6-55CF-474D-9DD1-A0A1163ADD32@yesql.se
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 28 Jul 2025, at 17:29, Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> wrote:

> To move this forward a tiny bit: I would be okay with maintaining a
> new getentropy() case. (I'm less excited about getrandom() because of
> its reduced reach.) And maybe down the line we should discuss choosing
> an option at configure time?

I would not be opposed to starting there.

--
Daniel Gustafsson

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David G. Johnston 2025-07-28 16:22:29 Re: vacuumdb changes for stats import/export
Previous Message Bruce Momjian 2025-07-28 16:12:02 Re: roles management problem after upgrading in PG 17