Re: Strange error (Socket command option unknown) - Mailing list pgsql-general

From Tom Lane
Subject Re: Strange error (Socket command option unknown)
Date
Msg-id 2917.1045977267@sss.pgh.pa.us
Whole thread Raw
In response to Strange error (Socket command option unknown)  (Carlos Moreno <moreno@mochima.com>)
List pgsql-general
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

pgsql-general by date:

Previous
From: Dima Tkach
Date:
Subject: Re: conexion entre servidores
Next
From: Dennis Gearon
Date:
Subject: 1 to many relationships