mirror of
https://github.com/postgres/postgres.git
synced 2026-05-28 04:35:45 -04:00
Doc: improve documentation about random().
We didn't explicitly say that random() uses a randomly-chosen seed
if you haven't called setseed(). Do so.
Also, remove ref/set.sgml's no-longer-accurate (and never very
relevant) statement that the seed value is multiplied by 2^31-1.
Back-patch to v12 where set.sgml's claim stopped being true.
The claim that we use a source of random bits as seed was debatable
before 4203842a1, too, so v12 seems like a good place to stop.
Per question from Carl Sopchak.
Discussion: https://postgr.es/m/f37bb937-9d99-08f0-4de7-80c91a3cfc2e@sopchak.me
This commit is contained in:
parent
32e1510150
commit
042554d55d
2 changed files with 4 additions and 2 deletions
|
|
@ -1171,6 +1171,9 @@
|
|||
subsequent <function>random()</function> calls in the current session are
|
||||
repeatable by re-issuing <function>setseed()</function> with the same
|
||||
argument.
|
||||
Without any prior <function>setseed()</function> call in the same
|
||||
session, the first <function>random()</function> call obtains a seed
|
||||
from a platform-dependent source of random bits.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
|
|
|
|||
|
|
@ -175,8 +175,7 @@ SET [ SESSION | LOCAL ] TIME ZONE { <replaceable class="parameter">timezone</rep
|
|||
<para>
|
||||
Sets the internal seed for the random number generator (the
|
||||
function <function>random</function>). Allowed values are
|
||||
floating-point numbers between -1 and 1, which are then
|
||||
multiplied by 2<superscript>31</superscript>-1.
|
||||
floating-point numbers between -1 and 1 inclusive.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
|
|
|
|||
Loading…
Reference in a new issue