"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
pgsql-bugs by date
|Next:||From: Michael Fuhr||Date: 2005-10-26 14:58:41|
|Subject: Re: BUG #2001: Signal 11 after concurrent inserts + updates|
|Previous:||From: Bruce Momjian||Date: 2005-10-26 14:49:12|
|Subject: Re: [BUGS] BUG #1993: Adding/subtracting negative time intervals|