From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
---|---|
To: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: random() function documentation |
Date: | 2022-04-12 08:19:07 |
Message-ID: | alpine.DEB.2.22.394.2204120950260.1378296@pseudo |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>>>> How about we just say "uses a linear-feedback shift register algorithm"?
>
> I think it'd be sufficient to just say that it's a deterministic
> pseudorandom number generator. I don't see much value in documenting
> the internal algorithm used.
Hmmm… I'm not so sure. ISTM that people interested in using the random
user-facing variants (only random?) could like a pointer on the algorithm
to check for the expected quality of the produced pseudo-random stream?
See attached.
>>> Should we perhaps also add a warning that the same seed is not
>>> guaranteed to produce the same sequence across different (major?)
>>> versions?
>>
>> I wouldn't bother, on the grounds that then we'd need such disclaimers
>> in a whole lot of places. Others might see it differently though.
>
> Agreed,
Agreed.
> though I think when the release notes are written, they ought
> to warn that the sequence will change with this release.
Yes.
--
Fabien.
Attachment | Content-Type | Size |
---|---|---|
random-algo.patch | text/x-diff | 1.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Smith | 2022-04-12 08:30:40 | Re: PG DOCS - logical replication filtering |
Previous Message | Julien Rouhaud | 2022-04-12 08:15:57 | Re: Unable to connect to Postgres13 server from psql client built on master |