Re: initial random incompatibility

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