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

From Fujii Masao
Subject Re: Suggestion to add --continue-client-on-abort option to pgbench
Date
Msg-id CAHGQGwGmwYOv6g3DGVLWZs7z4mXgay06ZdC3sfBtCnH0tLcOWg@mail.gmail.com
Whole thread Raw
In response to Re: Suggestion to add --continue-client-on-abort option to pgbench  (Chao Li <li.evan.chao@gmail.com>)
Responses Re: Suggestion to add --continue-client-on-abort option to pgbench
List pgsql-hackers
On Thu, Nov 13, 2025 at 11:21 AM Chao Li <li.evan.chao@gmail.com> wrote:
> I debugged further this morning, and I think I have found the root cause. Ultimately, the problem is not with
discardUntilSync(),instead, discardAvailableResults() mistakenly eats PGRES_PIPELINE_SYNC. 

Thanks for debugging!

Yes, discardAvailableResults() can discard PGRES_PIPELINE_SYNC,
but do you mean that's the root cause of the assertion failure
Nagata-san reported?
Since that failure can occur even in older branches, I was thinking
that newer code
like discardAvailableResults() in master isn't the root cause...

Regards,

--
Fujii Masao



pgsql-hackers by date:

Previous
From: jian he
Date:
Subject: Re: misleading error message in ProcessUtilitySlow T_CreateStatsStmt
Next
From: Chao Li
Date:
Subject: Re: SQL:2011 Application Time Update & Delete