Re: Re: pgbench randomness initialization
Chapman Flack <chap@anastigmatix.net>
From: Chapman Flack <chap@anastigmatix.net>
To: Fabien COELHO <coelho@cri.ensmp.fr>
Cc: PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Date: 2018-03-16T03:20:56Z
Lists: pgsql-hackers
I'm sorry, I must have missed your reply on the 5th somehow. On 03/05/18 07:01, Fabien COELHO wrote: > I must admit that I'm not too happy with the result as well, so I dropped > the octal/hexadecimal parsing. That seems perfectly reasonable to me; perfectly adequate to accept only one base. But now the documentation is back to its original state of silence on what base or how many bases might be allowed. Could it just say "or an unsigned decimal integer value"? Then no one will wonder. > The "idem" is about setting the variable but not overwritting it if it > already exists. The intention is that :random_seed is the random seed, > unless the user set it to something else in which case it is the user's > value. I've improved the variable description in the doc to point out that > the value may be overwritten with -D. Ok. -Chap
Commits
-
Set random seed for pgbench.
- 64f85894ad27 11.0 landed
-
Fix pgbench TAP test to work in VPATH builds.
- e94f2bc809a0 11.0 landed