From: Peter Koczan <pjkoczan@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: Pavan Deolasee <pavan.deolasee@gmail.com>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: Bus error in postgres 8.3
Date: Wed, 30 Apr 2008 15:38:41 -0500
Message-ID: <4544e0330804301338j1a44dc77r6981b8046404d960@mail.gmail.com> (raw)
In-Reply-To: <25410.1209448864@sss.pgh.pa.us>
References: <4544e0330804282205odfcac5al6bca78bd27c8751b@mail.gmail.com>
<25410.1209448864@sss.pgh.pa.us>
On Tue, Apr 29, 2008 at 1:01 AM, Tom Lane <tgl@sss.pgh.pa.us> 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 <pjkoczan@gmail.com> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: pjkoczan@gmail.com, tgl@sss.pgh.pa.us, pavan.deolasee@gmail.com
Subject: Re: Bus error in postgres 8.3
In-Reply-To: <4544e0330804301338j1a44dc77r6981b8046404d960@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox