On 8/8/16 10:46 AM, Christoph Berg wrote: >> 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?
For example, if you have a long-running update, it will run to completion even if you're no longer connected. This is arguably a feature.
