Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id D66E22E0057 for ; Wed, 30 Apr 2008 17:38:52 -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 82752-03 for ; Wed, 30 Apr 2008 17:38:46 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.191]) by developer.postgresql.org (Postfix) with ESMTP id D790E2E0052 for ; Wed, 30 Apr 2008 17:38:43 -0300 (ADT) Received: by nf-out-0910.google.com with SMTP id c7so309272nfi.23 for ; Wed, 30 Apr 2008 13:38:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=D2p/BIWMbBCDgxJiBjMPuiM0DZwZRFldYJv3/rG6dv4=; b=CEghzh1gJDXPXMXXHXAOLNwFDoj87ueBQkXzSPmbw5+3IcG7l+hFae0wz/U/gBerfIJC/t8hxXishAyPTsECbNCs8Zju2JUgo7k113I1nFhHCPQRZr2WDvqFIoQMi1xoL5trPec9rWHHcY9Wc1pMZu/nT/aQrBFAxbQBufc8Djk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=WR7tAgqOkBUEspB0kBn8LK0sPSt5+E3XXoDpy3lK4uv6wQYhlX/0ebpP25RzO3cLpMpZOqwiafzGn7szqDjcqLRB6/wxe/63Gy15HCwmKb29naKdtSwr/54r9QT28voPV1xberhWyM5mG1+l1Fv6f2QMHd5ZeaC9ckQoYSdHMB8= Received: by 10.150.79.42 with SMTP id c42mr1641857ybb.163.1209587921849; Wed, 30 Apr 2008 13:38:41 -0700 (PDT) Received: by 10.150.53.20 with HTTP; Wed, 30 Apr 2008 13:38:41 -0700 (PDT) Message-ID: <4544e0330804301338j1a44dc77r6981b8046404d960@mail.gmail.com> Date: Wed, 30 Apr 2008 15:38:41 -0500 From: "Peter Koczan" To: "Tom Lane" , "Pavan Deolasee" Subject: Re: Bus error in postgres 8.3 Cc: "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-Archive-Number: 200804/319 X-Sequence-Number: 29083 On Tue, Apr 29, 2008 at 1:01 AM, Tom Lane wrote: > 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. > On Tue, Apr 29, 2008 at 10:35 AM, Peter Koczan wrote: > Yeah, a stack trace and if possible, a self contained test case to > reproduce the bug would help. If you are using a custom build, then > using a debug build would help a lot too. So far, this problem hasn't reoccurred since I first saw it, no matter how much I pummel my test server. I was testing some patches about the time that this happened (including one in the libpq backend), so there may have been an ABI mismatch which led to the bus error. In any case, I've set the postmaster to have ulimit -c unlimited in case this problem reoccurs. I'll also look into using a debug build in case this happens again. But until then, I'm confident enough to keep pushing out 8.3. Thanks again. Peter