On Wed, 7 May 2008, Bruce Momjian wrote:
> Tom Lane wrote:
>> Greg Smith <gsmith(at)gregsmith(dot)com> writes:
>>> The way the option parsing code is done would make complaining in the case
>>> where your parameter is ignored a bit of a contortion.
>> Yeah. But couldn't we have that part issue a warning if -s had been set
>> on the command line?
> Patch attached that issues a warning.
Turns out it wasn't so contorted. Updated patch attached that only warns
in the exact cases where the setting is ignored, and the warning says how
it's actually setting the scale. I tested all the run types and it
correctly complains only when warranted, samples:
$ ./pgbench -s 200 -i pgbench
10000 tuples done. ...
$ ./pgbench -s 100 pgbench
Scale setting ignored by standard tests, using database branch count
transaction type: TPC-B (sort of)
scaling factor: 200 ...
$ ./pgbench -s 100 -f select.sql pgbench
transaction type: Custom query
scaling factor: 100 ...
* Greg Smith gsmith(at)gregsmith(dot)com http://www.gregsmith.com Baltimore, MD
In response to
pgsql-patches by date
|Next:||From: KaiGai Kohei||Date: 2008-05-09 10:10:32|
|Subject: Re: [0/4] Proposal of SE-PostgreSQL patches|
|Previous:||From: Bruce Momjian||Date: 2008-05-09 03:26:21|
|Subject: Re: [NOVICE] encoding problems|
pgsql-general by date
|Next:||From: Christian.Strobl||Date: 2008-05-09 08:31:48|
|Subject: reproducible database crash with simple sql command on postgres 8.3.1|
|Previous:||From: Luca Ferrari||Date: 2008-05-09 07:28:21|
|Subject: Re: regexp_replace in two times?|