On Wed, 13 Mar 2024 at 20:08, Jacob Champion <jacob.champ...@enterprisedb.com> wrote: > I hit this on my machine. With the attached diff I can reproduce > constantly (including with the most recent test patch); I think the > cancel must be arriving between the bind/execute steps?
Nice find! Your explanation makes total sense. Attached a patchset that fixes/works around this issue by using the simple query protocol in the cancel test.
v38-0001-Use-simple-query-protocol-for-cancel-test.patch
Description: Binary data
v38-0003-Start-using-new-libpq-cancel-APIs.patch
Description: Binary data
v38-0002-Revert-Comment-out-noisy-libpq_pipeline-test.patch
Description: Binary data
