Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 1065E2E003B for ; Thu, 1 May 2008 05:29:29 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 35452-07 for ; Thu, 1 May 2008 05:29:22 -0300 (ADT) X-Greylist: delayed 00:07:05.816086 by SQLgrey-1.7.5 Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.235]) by developer.postgresql.org (Postfix) with ESMTP id 02EC42E003A for ; Thu, 1 May 2008 05:29:24 -0300 (ADT) Received: by rv-out-0506.google.com with SMTP id b25so535448rvf.43 for ; Thu, 01 May 2008 01:29:23 -0700 (PDT) Received: by 10.141.23.7 with SMTP id a7mr735821rvj.5.1209630137731; Thu, 01 May 2008 01:22:17 -0700 (PDT) Received: by 10.140.174.16 with HTTP; Thu, 1 May 2008 01:22:17 -0700 (PDT) Message-ID: Date: Thu, 1 May 2008 10:22:17 +0200 From: "Filip Svendsen" To: "Tom Lane" Subject: Re: Bus error in postgres 8.3 Cc: "Peter Koczan" , "pgsql-admin@postgresql.org" In-Reply-To: <25410.1209448864@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4544e0330804282205odfcac5al6bca78bd27c8751b@mail.gmail.com> <25410.1209448864@sss.pgh.pa.us> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200805/1 X-Sequence-Number: 29085 On Tue, Apr 29, 2008 at 8:01 AM, Tom Lane wrote: > "Peter Koczan" writes: > > I'm going to try to force a crash on my test server to see if I can > > find out anything more. Does anyone know how to get useful debugging > > info at the time of the crash? I don't think I have things set to dump > > core anywhere, but that and/or stack traces would be nice (especially > > for child processes). > > Make sure the postmaster is started under ulimit -c unlimited. > On a depressingly large fraction of modern platforms, daemons are > started with ulimit -c 0 by default :-(. Try putting "ulimit -c unlimited" > into your PG init script and restarting. > > regards, tom lane Do you think a too low limit on user processes could be causing the problem? We have had similar crashes (server process terminated with Bus Error). This is running 8.2.5 on OS X (Tiger, intel), with about 130-140 connections, but the process count limit is 1000. Any reason why the process limit should be vastly higher than the number of connections? -- Venlig Hilsen / Kind Regards Filip Svendsen fs@basepointmedia.com