Skip site navigation (1) Skip section navigation (2)

Re: BUG #2576: tcp_keepalive doesn't work

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Fujii Masao <fujii(dot)masao(at)oss(dot)ntt(dot)co(dot)jp>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #2576: tcp_keepalive doesn't work
Date: 2006-08-18 13:00:53
Message-ID: 7342.1155906053@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Fujii Masao <fujii(dot)masao(at)oss(dot)ntt(dot)co(dot)jp> writes:
> Linux-Kernel Archive: Re: 2.6.12.5 bug? per-socket TCP keepalive settings
> http://www.ussg.iu.edu/hypermail/linux/kernel/0508.2/0757.html

> I'm confused whether tcp_keepalive problem should be solved
> at the DB level.

According to that, Linux keepalive starts working once you have either
sent or received at least one byte over the connection.  Therefore it's
not possible to get past the authentication stage without keepalive
being ready to go.  And we do have a pretty short timeout on the auth
stage (1 minute if memory serves).  So I'm not seeing what problem we
need to solve.

In any case, if you don't like that behavior methinks you need to be
lobbying some kernel hackers, not database weenies.  Postgres is not
in the business of second-guessing the TCP stack.

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: Joel StevensonDate: 2006-08-18 16:02:24
Subject: Website issue
Previous:From: Magnus HaganderDate: 2006-08-18 11:36:31
Subject: Re: BUG #2548: Fatal error with timezone

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group