Skip site navigation (1) Skip section navigation (2)

Re: BUG #2001: Signal 11 after concurrent inserts + updates

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Telin Lin" <tlin(at)rosettastone(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #2001: Signal 11 after concurrent inserts + updates
Date: 2005-10-26 14:49:46
Message-ID: 6047.1130338186@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
"Telin Lin" <tlin(at)rosettastone(dot)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

In response to

Responses

pgsql-bugs by date

Next:From: Michael FuhrDate: 2005-10-26 14:58:41
Subject: Re: BUG #2001: Signal 11 after concurrent inserts + updates
Previous:From: Bruce MomjianDate: 2005-10-26 14:49:12
Subject: Re: [BUGS] BUG #1993: Adding/subtracting negative time intervals

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group