Re: rand48 replacement

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Aleksander Alekseev <aleksander(at)timescale(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: rand48 replacement
Date: 2021-09-26 05:55:22
Message-ID: alpine.DEB.2.22.394.2109260742571.3216312@pseudo
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


>> Just FTR, I strongly object to your removal of process-startup srandom()
>> calls.
>
> Ok. The point of the patch is to replace and unify the postgres underlying
> PRNG, so there was some logic behind this removal.

FTR, this was triggered by your comment on Jul 1:

>> [...] I see that you probably did that because random.c and srandom.c
>> depend on it, but I wonder why we don't make an effort to flush those
>> altogether. It's surely pretty confusing to newbies that what appears
>> to be a call of the libc primitives is no such thing.

I understood "flushing s?random.c" as that it would be a good thing to
remove their definitions, hence their calls, whereas in the initial patch
I provided a replacement for srandom & random.

--
Fabien.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message wangsh.fnst@fujitsu.com 2021-09-26 08:40:15 RE: drop tablespace failed when location contains .. on win32
Previous Message Dilip Kumar 2021-09-26 05:51:52 Re: Gather performance analysis