Tatsuo Ishii is...@postgresql.org writes:
Does it support extended query? Does it support V3 protocol?
Yes.
It also has a proxy mode where it captures the queries sent by the
client along with think times and outputs that in the session format it
reads from its setup, which is very useful.
Tatsuo Ishii is...@postgresql.org writes:
I am thinking about to implement multi-master option for pgbench.
Please consider using Tsung, which solves that problem and many others.
http://tsung.erlang-projects.org/
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL :
Tatsuo Ishii is...@postgresql.org writes:
I am thinking about to implement multi-master option for pgbench.
Please consider using Tsung, which solves that problem and many others.
http://tsung.erlang-projects.org/
Thank you for introducing Tsung. I have some questions regarding it.
Does
On Wed, Aug 22, 2012 at 10:13:43AM +0900, Tatsuo Ishii wrote:
What does propagation of the writes mean?
I apologize for not being clear. In a multi-master system, people
frequently wish to know how quickly a write operation has been
duplicated to the other nodes. In some sense, those
Hi,
I am thinking about to implement multi-master option for pgbench.
Supose we have multiple PostgreSQL running on host1 and host2.
Something like pgbench -c 10 -h host1,host2... will create 5
connections to host1 and host2 and send queries to host1 and host2.
The point of this functionality is
On Tue, Aug 21, 2012 at 6:04 PM, Tatsuo Ishii is...@postgresql.org wrote:
Hi,
I am thinking about to implement multi-master option for pgbench.
Supose we have multiple PostgreSQL running on host1 and host2.
Something like pgbench -c 10 -h host1,host2... will create 5
connections to host1
Tatsuo Ishii is...@postgresql.org writes:
I am thinking about to implement multi-master option for pgbench.
Supose we have multiple PostgreSQL running on host1 and host2.
Something like pgbench -c 10 -h host1,host2... will create 5
connections to host1 and host2 and send queries to host1 and
I am thinking about to implement multi-master option for pgbench.
Supose we have multiple PostgreSQL running on host1 and host2.
Something like pgbench -c 10 -h host1,host2... will create 5
connections to host1 and host2 and send queries to host1 and host2.
The point of this functionality is
On Tue, Aug 21, 2012 at 06:04:42PM +0900, Tatsuo Ishii wrote:
Hi,
I am thinking about to implement multi-master option for pgbench.
Supose we have multiple PostgreSQL running on host1 and host2.
Something like pgbench -c 10 -h host1,host2... will create 5
connections to host1 and host2 and
I am thinking about to implement multi-master option for pgbench.
Supose we have multiple PostgreSQL running on host1 and host2.
Something like pgbench -c 10 -h host1,host2... will create 5
connections to host1 and host2 and send queries to host1 and host2.
The point of this functionality is
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. It will help developers to
enhance multi-master configuration in finding bugs and problems if
any. IMO I saw
Tatsuo Ishii is...@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
On Wed, Aug 22, 2012 at 06:26:00AM +0900, Tatsuo Ishii wrote:
I am thinking about to implement multi-master option for pgbench.
Supose we have multiple PostgreSQL running on host1 and host2.
Something like pgbench -c 10 -h host1,host2... will create 5
connections to host1 and host2 and
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
What does propagation of the writes mean?
I apologize for not being clear. In a multi-master system, people
frequently wish to know how quickly a write operation has been
duplicated to the other nodes. In some sense, those write operations
are incomplete until they have happened on all
Tatsuo Ishii is...@postgresql.org writes:
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
I do not intended to implement such a feature. As I wrote in the
subject line, I intended to enhance pgbench for multi-master
configuration. IMO, any node on multi-master configuration should
accept *any* queries, not only read queries but write queries. So bare
PostgreSQL streaming
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
The point of this functionality is to test some cluster
software which have a capability to create multi-master
configuration.
As the maintainer of software that does multi-master, I'm a little
confused as to why we would extend pg_bench
As the maintainer of software that does multi-master, I'm a little
confused as to why we would extend pg_bench to do this. The software
in question should be doing the testing itself, ideally via
it's test suite (i.e. make test). Having pg_bench do any of this
would be at best a very poor
19 matches
Mail list logo
