| From: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Daniel Gustafsson <daniel(at)yesql(dot)se>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Joe Conway <mail(at)joeconway(dot)com> |
| Subject: | Re: Support getrandom() for pg_strong_random() source |
| Date: | 2025-10-09 15:21:56 |
| Message-ID: | CAOYmi+mMdea2Oz+cASpHSSBZYCZzeoTj6jd09gQjnw4ju5jThg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Oct 6, 2025 at 4:11 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> Yeah.. I'm not sure that it is our job to draw a strict line, either.
> We are labelled as database specialists. When it comes to
> cryptography, I cannot say for all the others but I'm very confident
> in the fact that I'm bad at it.
Me too... but I do think we have to draw lines if we're going to
develop features on top of pg_strong_random.
--Jacob
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-10-09 15:22:39 | Re: Adding some error context for lock wait failures |
| Previous Message | Jacob Champion | 2025-10-09 15:20:26 | Re: Support getrandom() for pg_strong_random() source |