| From: | Andrej <andrej(dot)groups(at)gmail(dot)com> |
|---|---|
| To: | Steve Rosenberry <smrosenberry(at)electronicsolutionsco(dot)com> |
| Cc: | pgsql-novice <pgsql-novice(at)postgresql(dot)org> |
| Subject: | Re: Client query hangs when network connection is lost to the server. |
| Date: | 2013-04-09 22:12:09 |
| Message-ID: | CACMx3pPkWKshWYka_BWCf_XZaB=Z+JLw_m9Hfp9QsTKfeJ5rWA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
On 9 April 2013 16:48, Steve Rosenberry
<smrosenberry(at)electronicsolutionsco(dot)com> wrote:
>
> Call me stupid if you must, but I've tried both tcp_keepalive_xxx parameters and PQcancel() to abort a query to a remote server to which I've lost the network connection with no change in results. It appears to take about 15 minutes before the query gives up. I assume that must be due to some other system parameter that I cannot find. I can be very happy if I can shorten the 15 minute delay to about 30 to 60 seconds or have something else get me out the query in which I am stuck.
>
> Specifics below. Anything you need to know, just ask...
If I understand it correctly PQgetCancel operates against the server
side. So if you lost network connectivity
to the server the cancel won't make it there?
Cheers,
Andrej
| From | Date | Subject | |
|---|---|---|---|
| Next Message | kobolds | 2013-04-10 12:41:31 | about view privileges |
| Previous Message | Steve Rosenberry | 2013-04-09 04:48:24 | Client query hangs when network connection is lost to the server. |