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

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>
Cc: Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp>, 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-11-11 15:22:38
Message-ID: CAHGQGwFSW2g5Qf=Ws2xHaCT05vk2hLskXTXQ=y4no=W8byj++w@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Nov 11, 2025 at 11:41 AM Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com> wrote:
> I am also debugging the patch for the other purpose when I saw your email, so I tried to reproduce the problem with your script.
>
> I think in master branch, we can simply fix the problem by calling discardAvailableResults(st) before discardUntilSync(st), like this:

This change doesn't seem to fix the issue. If the custom script includes
many \syncpipeline commands, the assertion failure can still occur. No?

Regards,

--
Fujii Masao

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannu Krosing 2025-11-11 15:29:56 Patch: dumping tables data in multiple chunks in pg_dump
Previous Message Fujii Masao 2025-11-11 15:20:15 Re: Suggestion to add --continue-client-on-abort option to pgbench