Re: libpq copy error handling busted - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: libpq copy error handling busted
Date
Msg-id CA+hUKGLMPoyUaJ2XcJFQ+wnFxHTEDXhV5ZdBLjSmbHqwPvsQQw@mail.gmail.com
Whole thread Raw
In response to Re: libpq copy error handling busted  (Oleksandr Shulgin <oleksandr.shulgin@zalando.de>)
List pgsql-hackers
On Thu, Jun 4, 2020 at 6:22 PM Oleksandr Shulgin
<oleksandr.shulgin@zalando.de> wrote:
> On Thu, Jun 4, 2020 at 5:37 AM Thomas Munro <thomas.munro@gmail.com> wrote:
>> Here's what I tested.  First, I put this into pgdata/postgresql.conf:

> Would it be feasible to capture this in a sort of a regression (TAP?) test?

If I'm remembering correctly, it wouldn't work on Windows.  After
you've had an error sending to a socket, you can't receive (even if
there was something sent to you earlier).  At least that's how it
seemed from the experiments on that other thread.  The other problem
is that it requires inserting a sleep into the code...



pgsql-hackers by date:

Previous
From: Dilip Kumar
Date:
Subject: Re: PATCH: logical_work_mem and logical streaming of largein-progress transactions
Next
From: Jerome Wagner
Date:
Subject: Re: question regarding copyData containers