> setrandom: invalid maximum number 0
Okay, nevermind, user error: some other process was deleting a
row from pgbench_branches, and the pgbench.c happily set scale
to 0 from the 'select count(*) from pgbench_branches' query
inside of it, until it gives the totally not-helpful error
seen above
> > but the problem seems to only occur in >= 8.4. But it's also
Good news and bad news. The good news is that it started occuring on
all versions of pgbench, which makes it more likely to be a problem
with my system rather than pgbench (although that error message
sure is inscrutable). The ba
> That's not valid syntax. Some versions of getopt() take it upon
> themselves to rearrange the switch order, some do not ...
Sorry: I should have made clear this happens without the -n as well,
I just wanted to make the sample output a little smaller.
--
Greg Sabino Mullane g...@endpoint.com
Greg Sabino Mullane 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
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: