Thanks Gregory,
You right, of course, about that. It is 4 minutes I wasn't paying attention=
and thought that I have found something odd. The last packet is sent a min=
ute and a half after the first and I miss-read that for 20 seconds.
Cheers,
Val
--- On Wed, 16/7/08, Gregory Stark <stark@enterprisedb.com> wrote:
> From: Gregory Stark <stark@enterprisedb.com>
> Subject: Re: [BUGS] Psql or test application hangs when interface is down=
for the DB server
> To: valiouk@yahoo.co.uk
> Cc: "ext Tom Lane" <tgl@sss.pgh.pa.us>, "K, Niranjan (NSN - IN/Bangalore)=
" <niranjan.k@nsn.com>, pgsql-bugs@postgresql.org
> Date: Wednesday, 16 July, 2008, 6:33 PM
> "Valentin Bogdanov" <valiouk@yahoo.co.uk>
> writes:
>=20
> > I have noticed this as well. Blocks in poll(), timeout
> parameter -1,=20
>=20
> Oh good point. non-blocking sockets and poll/select let you
> control the
> timeout too.
>=20
> > meaning infinite then after 4 minutes on my system
> poll() returns 1 and
> > getsockopt() is called with SO_ERROR. SYN packets are
> tried only for the
> > default tcp timeout of 20 seconds.
>=20
> Uhm, 20 seconds would be an unreasonably low default. I
> think the RFCs mandate
> timeouts closer to the 4 minutes you describe.
>=20
> --=20
> Gregory Stark
> EnterpriseDB http://www.enterprisedb.com
> Ask me about EnterpriseDB's RemoteDBA services!
>=20
> --=20
> Sent via pgsql-bugs mailing list
> (pgsql-bugs@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-bugs
__________________________________________________________
Not happy with your email address?.
Get the one you really want - millions of new email addresses available now=
at Yahoo! http://uk.docs.yahoo.com/ymail/new.html