Re: BUG #3855: backend sends corrupted data on EHOSTDOWN error

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Scot Loach" <sloach(at)sandvine(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #3855: backend sends corrupted data on EHOSTDOWN error
Date: 2008-01-08 16:05:50
Message-ID: 9602.1199808350@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"Scot Loach" <sloach(at)sandvine(dot)com> writes:
> On FreeBSD, it is possible for a send() call on the backend socket to return
> an error code of EHOSTDOWN.

That's fine as long as the error condition is reasonably persistent.
I think what you are describing is a bug in FreeBSD's TCP stack: it
obviously isn't making adequately good-faith efforts to deliver the data
it's been handed.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2008-01-08 16:23:13 Re: 8.3.0 release schedule (Was:Re: [BUGS] BUG #3852: Could not create complex aggregate)
Previous Message Jochen Schwarz 2008-01-08 15:02:22 BUG #3857: pg_restore -t tablename doesn't restore constraints of this table