| From: | Sean Murphy <Sean(dot)Murphy(at)equipoint(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Idle session timeout? |
| Date: | 2007-05-08 17:19:25 |
| Message-ID: | 4640B11D.1010305@equipoint.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Tom Lane wrote:
> Sean Murphy <Sean(dot)Murphy(at)equipoint(dot)com> writes:
>> I'm WAY out of my depth here, but my impression, based on the
>> circumstances, is that there is some sort of an idle session timeout
>> kicking in (most likely on the client side) and dropping the connection.
>
> There's no such timeout in the Postgres server, for sure. I would
> actually bet that your problem is in some router between the client and
> the server. In particular, routers that do NAT address mapping
> typically have a timeout after which they will forget the mapping for an
> idle connection. If you've got one of those, see if it'll let you
> change the timeout.
>
> If you can't do that, you might think about teaching your client-side
> code to send dummy queries every so often.
>
> regards, tom lane
>
I've already maxed out the connection timeout at the firewall... and
I've been using dummy queries every five minutes, but it just feels like
a crutch to do so.
Sean
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gerard M | 2007-05-08 17:20:36 | Issue with database Postgresql :( |
| Previous Message | Jeff Davis | 2007-05-08 17:16:50 | Re: PITR and tar |