Re: Strange error (Socket command option unknown)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Carlos Moreno <moreno(at)mochima(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Strange error (Socket command option unknown)
Date: 2003-02-23 05:14:27
Message-ID: 2917.1045977267@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Carlos Moreno <moreno(at)mochima(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Dennis Gearon 2003-02-23 05:16:29 1 to many relationships
Previous Message Dima Tkach 2003-02-23 03:41:54 Re: conexion entre servidores