Re: pgbench randomness initialization
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Fabien COELHO <coelho@cri.ensmp.fr>, PostgreSQL Developers <pgsql-hackers@postgresql.org>, Robert Haas <robertmhaas@gmail.com>
Date: 2016-04-07T13:51:57Z
Lists: pgsql-hackers
On 2016-04-07 09:46:27 -0400, Tom Lane wrote: > Andres Freund <andres@anarazel.de> writes: > > On 2016-04-07 12:25:58 +0200, Fabien COELHO wrote: > >> So I have no mathematical doubt that changing the seed is the right default > >> setting, thus I think that the current behavior is fine. However I'm okay if > >> someone wants to control the randomness for some reason (maybe having "less > >> sure" results, but quickly), so it could be allowed somehow. > > > There might be some statistics arguments, but I think they're pretty > > ignoring reality. > > Sorry, but I think Fabien is right and you are wrong. Given that it's 3:1 so far, you might be right... > There is no point in having randomness in there at all if the thing is > constrained to generate the same "random" sequence every time. but that argument seems pretty absurd. It's obviously different to query for different rows over a run, rather than querying the same row again and again, in all backends. The reason we use randomness is to avoid easily discernible patterns in querying. Without randomness, how would you do that? Greetings, Andres Freund
Commits
-
Set random seed for pgbench.
- 64f85894ad27 11.0 landed
-
Fix pgbench TAP test to work in VPATH builds.
- e94f2bc809a0 11.0 landed