Tatsuo Ishii <ishii@postgresql.org> writes:
>> Why wouldn't you just fire up several copies of pgbench, one per host?
> Well, more convenient. Aside from bottle neck discussion below, simple
> tool to generate load is important IMO.
Well, my concern here is that it's *not* going to be simple. By the
time we get done adding enough switches to control connection to N
different hosts (possibly with different usernames, passwords, etc),
then adding frammishes to control which scripts get sent to which hosts,
and so on, I don't think it's really going to be simpler to use than
launching N copies of pgbench.
It might be worth doing if we had features that allowed the different
test scripts to interact, so that they could do things like check
replication propagation from one host to another. But pgbench hasn't
got that, and in multi-job mode really can't have that (at least not
in the Unix separate-processes implementation). Anyway that's a whole
nother level of complexity that would have to be added on before you
got to a useful feature.
regards, tom lane