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

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp>
Cc: Rintaro Ikeda <ikedarintarof(at)oss(dot)nttdata(dot)com>, Jakub Wartak <jakub(dot)wartak(at)enterprisedb(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-25 15:03:06
Message-ID: CAHGQGwGA965toJdD5nstCM5M05y2uayenyKF6xntR3C8GCbhcA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Sep 25, 2025 at 4:22 PM Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp> wrote:
> I've attached updated patches.

Thanks for updating the patches!

About 0001: you mentioned that the lost error message issue occurs in
pipeline mode.
Just to confirm, are you sure it never happens in non-pipeline mode?
From a quick look,
readCommandResponse() seems to have this problem regardless of whether pipeline
mode is used.

If it can also happen outside pipeline mode, maybe we should split this from
the assertion failure fix, since they'd need to be backpatched to
different branches.
What do you think?

Regards,

--
Fujii Masao

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alena Rybakina 2025-09-25 15:10:12 Re: Vacuum statistics
Previous Message Ashutosh Bapat 2025-09-25 14:56:16 Re: Report reorder buffer size