| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Darafei "Komяpa" Praliaskouski <me(at)komzpa(dot)net> |
| Cc: | Euler Taveira <euler(at)timbira(dot)com(dot)br>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Bruce Momjian <bruce(at)momjian(dot)us> |
| Subject: | Re: initial random incompatibility |
| Date: | 2019-06-17 17:09:24 |
| Message-ID: | 20190617170924.GA27809@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2019-Jun-17, Darafei "Komяpa" Praliaskouski wrote:
> I cannot find traces, but I believe there was a Twitter poll on which
> random do people get after setseed() in postgres, and we found at least
> three distinct sequences across different builds.
In different machines or different build options? I suppose that's
acceptable ... the problem is changing the sequence in one release to
the next in the same machine with the same build options.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2019-06-17 17:28:19 | Re: assertion at postmaster start |
| Previous Message | Darafei Komяpa Praliaskouski | 2019-06-17 16:55:44 | Re: initial random incompatibility |