Re: [PATCH] pgbench: add multiconnect option

From: "Imseih (AWS), Sami" <simseih(at)amazon(dot)com>
To: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, Greg Stark <stark(at)mit(dot)edu>
Cc: David Christensen <david(dot)christensen(at)crunchydata(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] pgbench: add multiconnect option
Date: 2022-03-18 17:32:45
Message-ID: 4915EE96-CDA2-4BDA-A56D-BC21E1A7539E@amazon.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

The current version of the patch does not apply, so I could not test it.

Here are some comments I have.

Pgbench is a simple benchmark tool by design, and I wonder if adding
a multiconnect feature will cause pgbench to be used incorrectly.
A real world use-case will be helpful for this thread.

For the current patch, Should the report also cover per-database statistics (tps/latency/etc.) ?

Regards,

Sami Imseih
Amazon Web Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2022-03-18 18:51:43 Re: Probable CF bot degradation
Previous Message Justin Pryzby 2022-03-18 17:32:25 Re: Remove INT64_FORMAT in translatable strings