Re: Strange error (Socket command option unknown)

Carlos Moreno <moreno@mochima.com> writes:
> "FATAL 1: Socket command option e unknown"

You sure it doesn't say
    Socket command type e unknown
?  Because that's how it's spelled in tcop/postgres.c, and I don't see
any other messages like this.

This message is basically saying that the backend got an unexpected
start-of-message character from the frontend.  Usually this happens
because the frontend and backend have gotten out of sync, and the most
common cause of that is a failed COPY IN operation.  COPY IN has no
error-recovery ability worthy of the name :-(.

Does your app use COPY IN a lot?  What shows up in the postmaster log
right before these messages?

            regards, tom lane