think this is still a bug that should be fixed in the backend code.
>
> scot.
>
>
> -Original Message-
> From: Jeff Davis [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, January 08, 2008 2:40 PM
> To: Scot Loach
> Cc: pgsql-bugs@postgresql.org
> Subject:
] BUG #3855: backend sends corrupted data
onEHOSTDOWNerror
On Tue, 2008-01-08 at 14:06 -0500, Scot Loach wrote:
> I agree this would be fine if PostgreSQL works the way you say below.
>
> However, PostgreSQL does not look at the # of bytes written and
> continue sending after tha
On Tue, 2008-01-08 at 14:06 -0500, Scot Loach wrote:
> I agree this would be fine if PostgreSQL works the way you say below.
>
> However, PostgreSQL does not look at the # of bytes written and continue
> sending after that many bytes. PostgreSQL actually simply clears its
> buffer of bytes to sen
t set, there was simply a
fragment of it missing.
scot.
-Original Message-
From: Jeff Davis [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 08, 2008 2:02 PM
To: Scot Loach
Cc: pgsql-bugs@postgresql.org
Subject: RE: [BUGS] BUG #3855: backend sends corrupted data
onEHOSTDOWNerror
O
