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

From Jeff Davis
Subject Re: possible bug not in open items
Date
Msg-id 1238188077.5525.3.camel@dell.linuxdev.us.dell.com
Whole thread Raw
In response to Re: possible bug not in open items  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Fri, 2009-03-27 at 15:43 -0400, Tom Lane wrote:
> 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.
>

That's perfectly acceptable to me. I'm only concerned about the shutdown
case, and that's the only case that's in conflict with the docs.

Regards,
    Jeff Davis

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: possible bug not in open items
Next
From: Jeff Davis
Date:
Subject: Re: possible bug not in open items