Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 779BD9FA3B3 for ; Fri, 20 Oct 2006 11:39:48 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 65006-06 for ; Fri, 20 Oct 2006 14:39:37 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 1DDB49F9F0A for ; Fri, 20 Oct 2006 11:39:36 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k9KEdXOJ008392; Fri, 20 Oct 2006 10:39:34 -0400 (EDT) To: Cedric BUSCHINI cc: pgsql-admin@postgresql.org Subject: Re: FATAL error frontend message invalid In-reply-to: <4538C9AB.4060307@carax.com> References: <4538C9AB.4060307@carax.com> Comments: In-reply-to Cedric BUSCHINI message dated "Fri, 20 Oct 2006 15:05:47 +0200" Date: Fri, 20 Oct 2006 10:39:33 -0400 Message-ID: <8391.1161355173@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200610/125 X-Sequence-Number: 23428 Cedric BUSCHINI writes: > I have a "weird" fatal line in logs: > FATAL: invalid frontend message type 48 48 == ASCII '0', so I'm betting that this represents the backend thinking that a new message starts in the middle of some text. In other words, most likely the client sent a malformed message. You need to figure out exactly which client is causing it --- enabling log_connections and adding ID info to log_line_prefix may help. regards, tom lane