Re: [PATCH] pgbench: add multiconnect option
От | Fabien COELHO |
---|---|
Тема | Re: [PATCH] pgbench: add multiconnect option |
Дата | |
Msg-id | alpine.DEB.2.22.394.2203191725001.1545063@pseudo обсуждение исходный текст |
Ответ на | Re: [PATCH] pgbench: add multiconnect option ("Imseih (AWS), Sami" <simseih@amazon.com>) |
Ответы |
Re: [PATCH] pgbench: add multiconnect option
|
Список | pgsql-hackers |
Hi Sami, > Pgbench is a simple benchmark tool by design, and I wonder if adding > a multiconnect feature will cause pgbench to be used incorrectly. Maybe, but I do not see how it would be worse that what pgbench already allows. > A real world use-case will be helpful for this thread. Basically more versatile testing for non single host setups. For instance, it would allow testing directly a multi-master setup, such as bucardo, symmetricds or coackroachdb. It would be a first step on the path to allow interesting features such as: - testing failover setup, on connection error a client could connect to another host. - testing a primary/standby setup, with write transactions sent to the primary and read transactions sent to the standbyes. Basically I have no doubt that it can be useful. > For the current patch, Should the report also cover per-database > statistics (tps/latency/etc.) ? That could be a "per-connection" option. If there is a reasonable use case I think that it would be an easy enough feature to implement. Attached a rebased version. -- Fabien.
Вложения
В списке pgsql-hackers по дате отправления: