Greg Sabino Mullane <g...@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
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
