Re: Clients disconnect but query still runs

From: Greg Stark <gsstark(at)mit(dot)edu>
To: Tatsuo Ishii <ishii(at)postgresql(dot)org>
Cc: jasen(at)xnet(dot)co(dot)nz, pgsql-general(at)postgresql(dot)org
Subject: Re: Clients disconnect but query still runs
Date: 2009-07-30 08:54:52
Message-ID: 407d949e0907300154n169c5713p7722bf7bf753e08f@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Jul 30, 2009 at 8:41 AM, Tatsuo Ishii<ishii(at)postgresql(dot)org> wrote:
>> Well SIGPIPE is no help since it would only fire if we tried to write
>> to the socket anyways.
>
> Right. For this purpose, pgpool sends param packet to client
> periodically while waiting for a reply from backend to detect if the
> connection to the client is broken. If it's broken, pgool sends cancel
> packet to backend not to waste backend machine's CPU cycle.

The downside to this is that it will cause spurious failures for
transient network failures even if the network comes back before it's
actually needed.

--
greg
http://mit.edu/~gsstark/resume.pdf

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Greg Stark 2009-07-30 09:02:44 Re: Clients disconnect but query still runs
Previous Message Thomas Kellerer 2009-07-30 08:30:55 Re: pg_stat_activity undocumented?