Re: Failed pgbench: setrandom invalid maximum number 0 - Mailing list pgsql-bugs

From Tom Lane
Subject Re: Failed pgbench: setrandom invalid maximum number 0
Date
Msg-id 8072.1306641301@sss.pgh.pa.us
Whole thread Raw
In response to Failed pgbench: setrandom invalid maximum number 0  (Greg Sabino Mullane <greg@endpoint.com>)
Responses Re: Failed pgbench: setrandom invalid maximum number 0
Re: Failed pgbench: setrandom invalid maximum number 0
Re: Failed pgbench: setrandom invalid maximum number 0
List pgsql-bugs
Greg Sabino Mullane <greg@endpoint.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

pgsql-bugs by date:

Previous
From: Greg Sabino Mullane
Date:
Subject: Failed pgbench: setrandom invalid maximum number 0
Next
From: Greg Sabino Mullane
Date:
Subject: Re: Failed pgbench: setrandom invalid maximum number 0