Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 38610B5DBE0 for ; Fri, 23 Sep 2011 18:03:50 -0300 (ADT) 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 70455-06 for ; Fri, 23 Sep 2011 21:03:43 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.8.0-rc2 Received: from joeconway.com (wsip-72-214-29-243.sd.sd.cox.net [72.214.29.243]) by mail.postgresql.org (Postfix) with ESMTP id 97557B5DBDA for ; Fri, 23 Sep 2011 18:03:43 -0300 (ADT) Received: from www.joeconway.com (account jconway [192.168.4.40] verified) by joeconway.com (CommuniGate Pro SMTP 4.1.8) with ESMTP-TLS id 11402442; Fri, 23 Sep 2011 14:03:42 -0700 Message-ID: <4E7CF42E.2050904@joeconway.com> Date: Fri, 23 Sep 2011 14:03:42 -0700 From: Joe Conway User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.0.12) Gecko/20071019 Fedora/1.5.0.12-3.fc6 pango-text Thunderbird/1.5.0.12 Mnenhy/0.7.5.666 MIME-Version: 1.0 To: "Burgholzer, Robert (DEQ)" CC: Scott Marlowe , pgsql-admin@postgresql.org Subject: Re: diagnosing a db crash - server exit code 2 References: <4E7CDCA6.6060803@joeconway.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-0.918 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RDNS_DYNAMIC=0.982 X-Spam-Level: X-Archive-Number: 201109/179 X-Sequence-Number: 38416 On 09/23/2011 01:45 PM, Burgholzer, Robert (DEQ) wrote: > Joe - it appears that it ALWAYS involves pLR - even a simple median call > has caused it, though I must say it is something that is calculating the > median of somewhere around 10-20,000 pieces of data if that makes any > difference. I would be delighted to run any kind of debugging necessary > and share the info. I have an identical system that can reproduce the > errors (I am pretty certain that they HAVE previously). What I DON'T > have is any knowledge of the stack-trace/debugger things, but I'm > willing to learn, and I have a sysadmin who may be able to lend a hand. There is some good information about using gdb with postgres here: http://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Linux/BSD If you need a hand, I would be happy to help you through the debugging via phone or even log in remotely if you can allow it. Just contact me off-list if you want to pursue that. Note that I made a new PL/R release just a few weeks ago which fixed several known crash-bugs. In particular these two pop out at me: - Fix missing calls to UNPROTECT. - Don't try to free an array element value when the array element is NULL Joe -- Joe Conway credativ LLC: http://www.credativ.us Linux, PostgreSQL, and general Open Source Training, Service, Consulting, & 24x7 Support