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.
> While fixing the breakage caused by the default number of trailing > digits output for real and double precision, I noticed that first > random() call after setseed(0) doesn't return the same value as 10 and > earlier (I tested 9.4 and later). It changed an expected behavior and > it should be listed in incompatibilities section of the release notes. > Some applications can rely on such behavior.