Re: [PATCH] pgbench: add multiconnect option

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: 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-16 09:28:57
Message-ID: alpine.DEB.2.22.394.2203161017060.843430@pseudo
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Hello Greg,

> It looks like David sent a patch and Fabien sent a followup patch. But
> there hasn't been a whole lot of discussion or further patches.
>
> It sounds like there are some basic questions about what the right
> interface should be. Are there specific questions that would be
> helpful for moving forward?

Review the designs and patches and tell us what you think?

Personnaly, I think that allowing multiple connections is a good thing,
especially if the code impact is reduced, which is the case with the
version I sent.

Then for me the next step would be to have a reconnection on errors so as
to implement a client-side failover policy that could help testing a
server-failover performance impact. I have done that internally but it
requires that "Pgbench Serialization and deadlock errors" to land, as it
would just be another error that can be handled.

--
Fabien.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bharath Rupireddy 2022-03-16 09:32:26 Re: add checkpoint stats of snapshot and mapping files of pg_logical dir
Previous Message Maxim Orlov 2022-03-16 08:53:33 Re: Add 64-bit XIDs into PostgreSQL 15