Re: possible bug not in open items - Mailing list pgsql-bugs

Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes:
> I'm not too familiar with this code, but I think we could just enable
> ImmediateInterruptOK in CopyGetData().

Only if you are wanting to break things.

The reason we don't allow client read to be interrupted is the fear of
losing protocol sync on an incomplete message.  For the SIGTERM case
this would (probably) be okay, since we aren't going to pay any more
attention to the client anyway, but accepting SIGINT there is right out.

            regards, tom lane