Re: [HACKERS] pgbench randomness initialization - Mailing list pgsql-hackers

From Fabien COELHO
Subject Re: [HACKERS] pgbench randomness initialization
Date
Msg-id alpine.DEB.2.20.1801021022420.20034@lancre
Whole thread Raw
In response to Re: pgbench randomness initialization  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: [HACKERS] pgbench randomness initialization
List pgsql-hackers
Hello Alvaro,

I revive this patch because controlling the seed is useful for tap testing 
pgbench.

> The output should include the random seed used, whether it was passed 
> with --random-seed, environment variable or randomly determined.  That 
> way, the user that later wants to verify why a particular run caused 
> some particular misbehavior knows what seed to use to reproduce that 
> run.

Yep.

Here is a new version which output use used seed when a seed is 
explicitely set with an option or from the environment.

However, the default (current) behavior remains silent, so no visible 
changes unless tinkering with it.

The patch also allows to use a "strong" random for seeding the PRNG, 
thanks to pg_strong_random().

The tests assume that stdlib random/srandom behavior is standard thus 
deterministic between platform.

-- 
Fabien.
Attachment

pgsql-hackers by date:

Previous
From: Rushabh Lathia
Date:
Subject: Re: [HACKERS] Parallel tuplesort (for parallel B-Tree index creation)
Next
From: Magnus Hagander
Date:
Subject: Re: Add default role 'pg_access_server_files'