X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 402E19FBA52 for ; Fri, 25 Aug 2006 10:44:43 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 43630-09 for ; Fri, 25 Aug 2006 10:44:38 -0300 (ADT) 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 830C19FBA4D for ; Fri, 25 Aug 2006 10:44:38 -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 k7PDiMuo023161; Fri, 25 Aug 2006 09:44:22 -0400 (EDT) To: "Donald Fraser" cc: "[ADMIN]" Subject: Re: Strange message followed by server crash In-reply-to: <003401c6c837$8dc6cb90$7d64a8c0@demolish1> References: <003401c6c837$8dc6cb90$7d64a8c0@demolish1> Comments: In-reply-to "Donald Fraser" message dated "Fri, 25 Aug 2006 12:13:54 +0100" Date: Fri, 25 Aug 2006 09:44:22 -0400 Message-ID: <23160.1156513462@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.143 tagged_above=0 required=5 tests=AWL, SPF_HELO_PASS, SPF_PASS X-Spam-Level: X-Archive-Number: 200608/284 X-Sequence-Number: 22827 "Donald Fraser" writes: > Log messages: > <1Tmenteshvili 10709 2006-08-24 17:48:19 BST 0> ERROR: invalid message format > < 3670 2006-08-24 17:48:19 BST > LOG: server process (PID 10709) was terminated by signal 11 > At the same time, an engineer, who thought nobody was in the building, was working on the network and changing a network switch. Hm, the "invalid message format" is unsurprising if the network suffered a glitch and delivered bad data, but the backend crash is not good. And what do you make of the apparent junk on the log line? (What's your log_line_prefix exactly?) Given that this sounds like it won't be easy to reproduce, I'm hoping you have a core file left from that and can get a stack trace from it. That would give us some clue where to look. regards, tom lane