Re: Failed pgbench: setrandom invalid maximum number 0

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Greg Sabino Mullane <greg(at)endpoint(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Failed pgbench: setrandom invalid maximum number 0
Date: 2011-05-29 03:55:01
Message-ID: 8072.1306641301@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Greg Sabino Mullane <greg(at)endpoint(dot)com> writes:
> Seeing the following on an old box I use for testing various
> things. Thought it was something to do with my box at first,
> but the problem seems to only occur in >= 8.4. But it's also
> not pgbench alone, as it was working fine one day, and not the
> next. Here's what I now get on 8.4, 9.0, and 9.1:

> $ pgbench btest1 -n

> setrandom: invalid maximum number 0

That's not valid syntax. Some versions of getopt() take it upon
themselves to rearrange the switch order, some do not ...

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Greg Sabino Mullane 2011-05-29 04:20:27 Re: Failed pgbench: setrandom invalid maximum number 0
Previous Message Greg Sabino Mullane 2011-05-29 03:11:56 Failed pgbench: setrandom invalid maximum number 0