Subject: Socket command type unknown X-FID: FLAVOR00-NONE-0000-0000-000000000000 X-Priority: 3 X-Antivirus: avast! (VPS 0418-4, 29/04/2004), Outbound message X-Antivirus-Status: Clean X-Virus-Scanned: by amavisd-new at postgresql.org X-Amavis-Alert: BAD HEADER Non-encoded 8-bit data (char E9 hex) in message header 'Date' Date: ... 14:54:26 +0200 (Paris, Madrid (heure d'\351t\351))\n ^ X-Spam-Status: No, hits=0.3 tagged_above=0.0 required=5.0 tests=HTML_50_60, HTML_MESSAGE, HTML_TAG_EXISTS_TBODY X-Spam-Level: X-Archive-Number: 200405/12 X-Sequence-Number: 4904 --------------Boundary-00=_QUNX8WA1VA4000000000 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello,=0D =0D I'm developping a deamon, written in C under "Linux RedHat 9".=0D I'm using ECPG to access my db.=0D The postgres version is 7.3.2 =0D =0D Sometimes I've got the "Socket command type unknown" error message displayed in my log file after a SELECT or an UPDATE, and then my daemon lose the connection with the postmaster ('no connection to the server' message).=0D =0D I found in the archives that the problem may be a bad synchonization between the backend (postmaster ?) and the frontend (my daemon / libpq ?). I understand that because the protocol is waiting for a 'Q' ("query") or an 'X ("exit") but I didn't found any solution !=0D =0D Have you any idea ?=0D =0D Thanks=0D =0D Philippe Sempe (France) --------------Boundary-00=_QUNX8WA1VA4000000000 Content-Type: Text/HTML; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hello,

I'm developping a deamon, written in C under "Linux Red= Hat 9".

I'm using ECPG to access my db.

The postgres version is 7.3.2

Sometimes I've got the "Socket command type unkno= wn" error message displayed in my log file after a SELECT or an UPDATE, and= then my daemon lose the connection with the postmaster ('no connection to = the server' message).

I found in the archives that the problem may be a = bad synchonization between the backend (postmaster ?) and the frontend (my = daemon / libpq ?). I understand that because the protocol is waiting for a = 'Q' ("query") or an 'X' ("exit") but I didn't found any solution !

Have you any idea ?

Thanks

Philippe Sempe (France)

--------------Boundary-00=_QUNX8WA1VA4000000000--