| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Tom Ivar Helbekkmo <tih(at)kpnQwest(dot)no> |
| Cc: | Bruce Badger <bbadger(at)BadgerSE(dot)com>, pgsql-interfaces(at)postgresql(dot)org |
| Subject: | Re: Beating Oracle |
| Date: | 2002-03-01 19:14:33 |
| Message-ID: | 29985.1015010073@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-interfaces |
Tom Ivar Helbekkmo <tih(at)kpnQwest(dot)no> writes:
>> Non-broken TCP stacks are normally quite tenacious about surviving
>> transmission glitches in already-open connections.
> ...but you can turn part of that off by turning on SO_KEEPALIVE.
In an RFC-compliant stack, the outage interval required before KEEPALIVE
will kill the connection is of the order of hours. RFC 1122 specifies
that the minimum interval before the first probe is even sent is 2 hours
(since last activity on connection), and that a single failed probe is
not sufficient reason to drop the connection.
RFC 2525 does note that excessively short keepalive timeout is a common
form of TCP-stack bug.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Klatt | 2002-03-01 19:15:36 | HeapTuple layout |
| Previous Message | Tom Ivar Helbekkmo | 2002-03-01 18:53:57 | Re: Beating Oracle |