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

From Tom Lane
Subject Re: BUG #2001: Signal 11 after concurrent inserts + updates
Date
Msg-id 6047.1130338186@sss.pgh.pa.us
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
"Telin Lin" <tlin@rosettastone.com> writes:
> My postgresql keeps crashing by signal 11 after a number of concurrent
> inserts + updates.

This could be due to corrupt data, or it could be a hardware problem ---
have you done any memory tests on that machine lately?  If you can
pg_dump the table involved without any failure, then the corrupt-data
hypothesis is probably ruled out.  Also, try to get a stack trace from
the core dump (if no core file, restart postmaster under ulimit -c
unlimited --- it's easiest to put that into the postgres init script).

            regards, tom lane

pgsql-bugs by date:

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