Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id B4297B5DBE0 for ; Fri, 23 Sep 2011 17:31:20 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 18139-04 for ; Fri, 23 Sep 2011 20:31:13 +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 5AFE7B5DBD1 for ; Fri, 23 Sep 2011 17:31:12 -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 11402389; Fri, 23 Sep 2011 13:31:12 -0700 Message-ID: <4E7CEC90.90306@joeconway.com> Date: Fri, 23 Sep 2011 13:31:12 -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: 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/175 X-Sequence-Number: 38412 On 09/23/2011 12:38 PM, Burgholzer, Robert (DEQ) wrote: > Thanks - I will try to check into this - however, we have done some > tuning on the memory over the last 2 years and gotten it such that it is > seldom if every having to dip into its swap too substantially -- > according to "top", we remain under 1% swap usage during most times. > Generally speaking, I run 3-5 of these large PHP processes > simultaneously with no issue, however, when I issue even a "median" > function call, after several calls (no consistent pattern that I can > discern), the backend crashes. Is this always related to use of PL/R or is it sometimes happening independently? If you believe it is PL/R specific, please give us R version and PL/R version. Also, any chance we can get a debugger on a core file? Can you reproduce this on a development machine? Thanks, Joe -- Joe Conway credativ LLC: http://www.credativ.us Linux, PostgreSQL, and general Open Source Training, Service, Consulting, & 24x7 Support