Re: Re: [HACKERS] pgbench randomness initialization

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Chapman Flack <chap(at)anastigmatix(dot)net>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: [HACKERS] pgbench randomness initialization
Date: 2018-01-18 22:29:59
Message-ID: alpine.DEB.2.20.1801182327580.25275@lancre
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

> Here is a rebase, plus some more changes:
> I have improved the error message to tell from where the value was provided.
> I have removed the test to the exact values produced from the expression test
> run.
> I have added a test which run from the same seed value several times
> and checks that the output values are the same.

This version adds a :random_seed script variable, for information.


Attachment Content-Type Size
pgbench-seed-7.patch text/x-diff 12.1 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2018-01-18 23:15:09 Re: [HACKERS] Refactor handling of database attributes between pg_dump and pg_dumpall
Previous Message Alexander Korotkov 2018-01-18 22:16:56 Re: Index-only scan returns incorrect results when using a composite GIST index with a gist_trgm_ops column.