This may be true, but I still think PostgreSQL should be more defensive
and actively terminate the connection when this happens (like ssh does)
scot.
=20
-----Original Message-----
From: Jeff Davis [mailto:pgsql@j-davis.com]=20
Sent: Tuesday, January 08, 2008 12:52 PM
To: Scot Loach
Cc: pgsql-bugs@postgresql.org
Subject: Re: [BUGS] BUG #3855: backend sends corrupted data on
EHOSTDOWNerror
On Tue, 2008-01-08 at 01:50 +0000, Scot Loach wrote:
> The following bug has been logged online:
>=20
> Bug reference: 3855
> Logged by: Scot Loach
> Email address: sloach@sandvine.com
> PostgreSQL version: 8.2.4
> Operating system: freebsd 6.1
> Description: backend sends corrupted data on EHOSTDOWN error
> Details:=20
>=20
This is a FreeBSD bug.=20
http://www.freebsd.org/cgi/query-pr.cgi?pr=3D100172
It has been fixed here:
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/netinet/tcp_output.c
in revision 1.112.2.1.
I ran into this bug too, and it was very frustrating! For me, it
manifested itself as SSL errors.
You can demonstrate the problem with SSH as well (inducing an ARP
failure will terminate the SSH session, when TCP should protect you
against that), so it is clearly not a PostgreSQL bug.
Thanks to "Andrew - Supernews" (a PostgreSQL user) for tracking this bug
down.
Regards,
Jeff Davis
