Re: Socket command type N unknown

"Havrylyak Roma" <roma(at)ukr(dot)net> writes:
> The first and last notice are mine from stored procedures.
> But what about second and third noticies. How can I debug where the error
> occur???
> What such error "Socket command type N unknown" is stand for???

> Nov 14 17:07:18 empire logger: NOTICE: cost=0.0829333, interval=00:10:22
> Nov 14 17:07:18 empire logger: FATAL 1: Socket command type N unknown
> Nov 14 17:07:18 empire logger: NOTICE: AbortTransaction and not in
> in-progress state
> Nov 14 17:07:34 empire logger: NOTICE: found, start=2000-11-14 16:56:00+02
> , finish=2000-11-14 17:08:43+02, koridor=2000-11-14 09:00:00+02

The "socket command" complaint suggests that the frontend and backend
got out of sync --- the backend was expecting a new command character
('Q' for query, 'F' for fastpath function call, or 'X' for exit) but
got an 'N' instead. Unless your frontend client is totally broken,
it'd never have sent an 'N' to start a command; more likely the 'N'
is part of the data part of some command string. How this happened
I can't tell from the given info. What does your client look like?

regards, tom lane