From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | David(dot)Bear(at)asu(dot)edu |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: long term persistent tunnels |
Date: | 2004-08-20 00:38:52 |
Message-ID: | 14201.1092962332@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
David Bear <David(dot)Bear(at)asu(dot)edu> writes:
> Asume I have another server called web1 that will be connecting to db1
> for data base operations. If I setup an ssh tunnel should I be aware
> of any problems with 1) spontaneously dropped connections...2) long
> term time out -- 3)other?
In theory the connection won't be dropped until the client drops it or
the database is shut down.
In practice, the only major problems I've heard about have to do with
connections that go through a NAT (address-mapping) firewall. A NAT
firewall has to keep a table of open connections, and some of them seem
to drop their entries for idle connections with unseemly haste (like
less than the RFC-mandated timeouts).
If you've got one of these suckers to deal with, the only solution is to
make sure there's some activity on the connection at least once every
few minutes.
If web1 and db1 are on the same LAN then you probably have nothing to
fear.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Pradeepkumar, Pyatalo (IE10) | 2004-08-20 04:41:17 | problem with setting PATH variable |
Previous Message | David Bear | 2004-08-19 23:29:30 | long term persistent tunnels |