Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 9AD9B9FB4C6 for ; Thu, 10 May 2007 12:12:59 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 23564-04 for ; Thu, 10 May 2007 12:12:55 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 76D589FB378 for ; Thu, 10 May 2007 12:12:55 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id l4AFCpZl013627; Thu, 10 May 2007 11:12:51 -0400 (EDT) To: Szabolcs BALLA cc: Postgresql Admin Subject: Re: Invalid frontend message type 87? In-reply-to: <4642D9AD.8060904@confinsystems.com> References: <4642D9AD.8060904@confinsystems.com> Comments: In-reply-to Szabolcs BALLA message dated "Thu, 10 May 2007 10:37:01 +0200" Date: Thu, 10 May 2007 11:12:51 -0400 Message-ID: <13626.1178809971@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/83 X-Sequence-Number: 25403 Szabolcs BALLA writes: > I have a problem with postgresql 8.1.4. and libpq 4. > I found this error message in the log file: PGRES_FATAL_ERROR invalid frontend message type 87 "Invalid frontend message" means the server got a message with an unexpected first byte, which usually means the server and libpq got out of sync about where the message boundaries are. It's been quite a long time since we've seen an actual bug of that sort, though. The cases that I've heard of recently involve multiple threads in an application trying to use the same PGconn without any interlocking. You can't have multiple queries active on a single connection, but libpq itself doesn't contain any locking to prevent multiple threads from trying to use the PGconn at once. If you're getting this with a single-threaded client, please submit a test case to pgsql-bugs. regards, tom lane