Re: Suggestion to add --continue-client-on-abort option to pgbench - Mailing list pgsql-hackers

From Dilip Kumar
Subject Re: Suggestion to add --continue-client-on-abort option to pgbench
Date
Msg-id CAFiTN-v6biSNm0uUDDEMSD=DTcWXhbA7KonjAGOhtYLWg8o7Og@mail.gmail.com
Whole thread Raw
In response to Re: Suggestion to add --continue-client-on-abort option to pgbench  (Stepan Neretin <slpmcf@gmail.com>)
Responses Re: Suggestion to add --continue-client-on-abort option to pgbench
List pgsql-hackers
On Tue, May 13, 2025 at 9:20 AM <Rintaro.Ikeda@nttdata.com> wrote:
> I also appreciate you for pointing out my mistakes in the previous version of the patch. I fixed the duplicated
lines.I’ve attached the updated patch. 
>
This is a useful feature, so +1 from my side.  Here are some initial
comments on the patch while having a quick look.

1. You need to update the stats for this new counter in the
"accumStats()" function.

2. IMHO, " continue-on-error " is more user-friendly than
"continue-client-on-error".

3. There are a lot of whitespace errors, so those can be fixed.  You
can just try to apply using git am, and it will report those
whitespace warnings.  And for fixing, you can just use
"--whitespace=fix" along with git am.

--
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Yasir
Date:
Subject: Re: Why our Valgrind reports suck
Next
From: Laurenz Albe
Date:
Subject: Re: PG 18 release notes draft committed