Re: "unexpected EOF" messages - Mailing list pgsql-hackers

From Tom Lane
Subject Re: "unexpected EOF" messages
Date
Msg-id 8839.1336067293@sss.pgh.pa.us
Whole thread Raw
In response to Re: "unexpected EOF" messages  (Magnus Hagander <magnus@hagander.net>)
Responses Re: "unexpected EOF" messages
List pgsql-hackers
Magnus Hagander <magnus@hagander.net> writes:
> Heh - we already used ERRCODE_CONNECTION_FAILURE on the errors in
> copy.c. Since COPY can only happen when there is a transaction
> (right?), I just changed those error messages for consistency.

Agreed on changing the message texts to match, but I wonder whether
we ought not switch all those SQLSTATEs to something different.  Per my
comment to Kevin, I think the whole 08 class is meant to be issued on
the client side.  Maybe it's okay to conflate a server-detected
connection loss with client-detected loss, but I'm not convinced.
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: "unexpected EOF" messages
Next
From: Andres Freund
Date:
Subject: Re: Advisory locks seem rather broken