Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 0429F1337B4F for ; Mon, 29 Nov 2010 20:21:49 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 07366-10 for ; Tue, 30 Nov 2010 00:21:42 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from na3sys009aog103.obsmtp.com (na3sys009aog103.obsmtp.com [74.125.149.71]) by mail.postgresql.org (Postfix) with SMTP id 5C06E1337B39 for ; Mon, 29 Nov 2010 20:21:41 -0400 (AST) Received: from source ([209.85.214.177]) by na3sys009aob103.postini.com ([74.125.148.12]) with SMTP ID DSNKTPRDleTRHSrjADesPGcoqmSDinL6GbZ6@postini.com; Mon, 29 Nov 2010 16:21:42 PST Received: by mail-iw0-f177.google.com with SMTP id 36so745803iwn.36 for ; Mon, 29 Nov 2010 16:21:41 -0800 (PST) Received: by 10.231.145.209 with SMTP id e17mr63723ibv.8.1291076488032; Mon, 29 Nov 2010 16:21:28 -0800 (PST) From: Michael Holt References: <8a0b69864ef0bd962213ad553c113a44@mail.gmail.com> <7916.1291075781@sss.pgh.pa.us> In-Reply-To: <7916.1291075781@sss.pgh.pa.us> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcuQIuN75GkHxHzxTX6TP22KB6SgDAAAZiVQ Date: Mon, 29 Nov 2010 16:21:27 -0800 Message-ID: <9c40262b2d69c40bea6b744ceb8ec6f0@mail.gmail.com> Subject: Re: Diagnosing Postgres Segfault To: Tom Lane Cc: pgsql-admin@postgresql.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-4.2 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3 X-Spam-Level: X-Archive-Number: 201011/244 X-Sequence-Number: 36210 Doesn't look like it at the moment. I'll see if we can get that setup and go from there. Thanks. -----Original Message----- From: Tom Lane [mailto:tgl@sss.pgh.pa.us] Sent: Monday, November 29, 2010 4:10 PM To: Michael Holt Cc: pgsql-admin@postgresql.org Subject: Re: [ADMIN] Diagnosing Postgres Segfault Michael Holt writes: > I'm trying to figure out what might have caused this, partly because I want > to replicate the segfault to see if it is the cause of another system > randomly freezing on us. Is there any way to figure out exactly what query > being run at the time of the crash was doing? Is there a core dump file? If so, a stack trace from that might be informative. regards, tom lane