Re: BUG #2001: Signal 11 after concurrent inserts + updates - Mailing list pgsql-bugs

From Michael Fuhr
Subject Re: BUG #2001: Signal 11 after concurrent inserts + updates
Date
Msg-id 20051026145841.GA24988@winnie.fuhr.org
Whole thread Raw
In response to BUG #2001: Signal 11 after concurrent inserts + updates  ("Telin Lin" <tlin@rosettastone.com>)
Responses Re: BUG #2001: Signal 11 after concurrent inserts + updates
List pgsql-bugs
On Wed, Oct 26, 2005 at 09:27:52AM +0100, Telin Lin wrote:
> My postgresql keeps crashing by signal 11 after a number of concurrent
> inserts + updates.

Did you get a core dump?  If so, can you get a stack trace from it?
In released versions of PostgreSQL core dumps are usually found
under the $PGDATA/base/<database oid> directory unless your system
is configured to put them elsewhere.  If you got no core dump then
you might need to adjust the coredumpsize resource limit that the
postmaster runs with.

You mentioned that you were using Slony.  Do you have any other
add-ons?  Custom data types, third-party modules, etc.?

--
Michael Fuhr

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #2001: Signal 11 after concurrent inserts + updates
Next
From: Seneca Cunningham
Date:
Subject: Re: BUG #1999: contrib/spi doesn't receive the configured