Hi,
Currently, pgbench processes a copy response as unexpected and will
move to the error loop. However, PQgetResult will alway return an
empty result when there's no async result through getCopyResult,
leading to an infinite loop in the error handling as res will never be
NULL.
This patch forcef
On Thu, Oct 2, 2025 at 10:27 AM Michael Paquier wrote:
> Fun. It seems like nobody has ever tested this scenario, even for a
> COPY TO. Why did you try that? Did you have a benchmark scenario in
> mind?
I was trying to trigger pipeline errors while reviewing the
--continue-client-on-abort pgbe
On Wed, Oct 01, 2025 at 11:25:00AM +0200, Anthonin Bonnefoy wrote:
> Currently, pgbench processes a copy response as unexpected and will
> move to the error loop. However, PQgetResult will alway return an
> empty result when there's no async result through getCopyResult,
> leading to an infinite lo
