Re: [BUGS] Errors in one program and not in another... CODE is identical - Mailing list pgsql-bugs

From Tom Lane
Subject Re: [BUGS] Errors in one program and not in another... CODE is identical
Date
Msg-id 3493.938614371@sss.pgh.pa.us
Whole thread Raw
In response to Errors in one program and not in another... CODE is identical  (Trever Adams <trever_Adams@bigfoot.com>)
List pgsql-bugs
Trever Adams <trever_Adams@bigfoot.com> writes:
> [pid  3270] write(2, "FATAL 1:  Socket command type P unknown\n\n", 41)
> = 41
> [pid  3270] write(4, "EFATAL 1:  Socket command type P unknown\n\n\0",
> 43) = 43

> I get data back from the first select, but the above errors seem to
> follow right after.

That looks like the client and backend are getting out of sync.  The
backend expects query commands from the client to be preceded by 'Q'
(there are also 'F' and 'X' command types, IIRC), and this complaint
says that the next character it read after processing a command wasn't
one of the expected command types.  Probably that 'P' is out of the
middle of some query string sent by the client.

How they got out of sync I can't tell from this much info.  Are you
using libpq, or some other interface?

            regards, tom lane

pgsql-bugs by date:

Previous
From: "David Godin"
Date:
Subject: Installing PostgreSQL
Next
From: Mark Dalphin
Date:
Subject: Problem with pg_dump and functions