[Pkg-postgresql-public] Bug#255208: Bug#255208: obsolete?

Christoph Berg myon at debian.org
Mon Aug 8 14:46:08 UTC 2016

Re: Peter Eisentraut 2016-08-08 <1e904e8c-0abc-71ac-6d19-bb7255cecd6d at debian.org>
> On 8/8/16 10:05 AM, Christoph Berg wrote:
> > I'm still curious why PG doesn't just cancel the query by itself on
> > SIGPIPE. Is there any value in running queries to completion when the
> > user has already left? Are these queries even committed?
> I haven't tested this in detail for local socket connections, but for
> TCP/IP, the backend carries on if the client disappears.  The
> server-side TCP keepalive settings are there to control this to some extent.

I mean... why? If PG receives SIGPIPE in that case (I haven't tested
it, but I believe it does), why carry on?

(Of course TCP keepalive is still useful for the cases where the remote
OS didn't send a RST, but when it does, why not use it?)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-postgresql-public/attachments/20160808/4dc9cc8a/attachment.sig>

More information about the Pkg-postgresql-public mailing list