Re: Suggestion to add --continue-client-on-abort option to pgbench

From: Jakub Wartak <jakub(dot)wartak(at)enterprisedb(dot)com>
To: Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp>
Cc: Rintaro Ikeda <ikedarintarof(at)oss(dot)nttdata(dot)com>, "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, "slpmcf(at)gmail(dot)com" <slpmcf(at)gmail(dot)com>, "boekewurm+postgres(at)gmail(dot)com" <boekewurm+postgres(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Srinath Reddy Sadipiralla <srinath2133(at)gmail(dot)com>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>
Subject: Re: Suggestion to add --continue-client-on-abort option to pgbench
Date: 2025-09-16 08:34:03
Message-ID: CAKZiRmyV3LBj3Ev-FOty71my114-mBuaMPqXb5R4rwLvzRn+cw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jul 24, 2025 at 5:44 AM Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp> wrote:

> >
> > I believe the patches implement the expected behavior, include appropriste doc and test
> > modification, are in good shape overall, so if there are no objections,
> > I'll mark this as Read-for-Committer.
>
> I've updated the CF status to Ready for Committer.

Thanks for working on it! As Matthias, Dilip, Srinath and many others
pointed out it would be a very nice and helpful addition to pgbench.
I've just used it out of necessity and it worked as advertised for me
and it even adds a cool-looking "XXX failed" when used with -P
progress meter:

progress: 1.0 s, 0.0 tps, lat 0.000 ms stddev 0.000, 3854 failed
progress: 2.0 s, 0.0 tps, lat 0.000 ms stddev 0.000, 3796 failed

-J.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2025-09-16 08:34:34 Re: Conflict detection for update_deleted in logical replication
Previous Message Amit Kapila 2025-09-16 08:29:55 Re: POC: enable logical decoding when wal_level = 'replica' without a server restart