On Tue, Apr 29, 2008 at 1:01 AM, Tom Lane <tgl@[EMAIL PROTECTED]
> 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@[EMAIL PROTECTED]
>
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
pu****ng out 8.3.
Thanks again.
Peter
--
Sent via pgsql-admin mailing list (pgsql-admin@[EMAIL PROTECTED]
)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
|
