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

2005-10-27 Thread Michael Fuhr
[Please copy the mailing list on replies.] On Thu, Oct 27, 2005 at 10:54:51AM -0400, Telin Lin wrote: > I have just got a 17M coredump. Do you have a preferred way for me to > sent that to you? I can always place it on a ftp site for you > download. Thank you. Please post the stack trace fro

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

2005-10-27 Thread Telin Lin
No, haven't done any memory tests lately. Let me get that going. I am doing pg_dump nightly with the whole database including this table. so i guess that says it. I couldn't find any core dump. btw, the core dump filename should be just like 'coredump', right? Let me also get the max_sta

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

2005-10-27 Thread Telin Lin
I have several directories such as 1, 17229, 17230, 333909 under base. but none of them is generated during crash time. Under thsoe directories, there are a bunch of files with (number) filename. Some of them are over size of 6M. I guess i will set the max_stack_depth in postgres.con

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

2005-10-26 Thread Tom Lane
Telin Lin <[EMAIL PROTECTED]> writes: > the core dump filename should be just like 'coredump', right? Probably either "core" or "core." kind of name. In existing PG releases you'll usually find it under $PGDATA/base// regards, tom lane --

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

2005-10-26 Thread Michael Fuhr
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 $PG

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

2005-10-26 Thread Tom Lane
"Telin Lin" <[EMAIL PROTECTED]> 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 involv

[BUGS] BUG #2001: Signal 11 after concurrent inserts + updates

2005-10-26 Thread Telin Lin
The following bug has been logged online: Bug reference: 2001 Logged by: Telin Lin Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0.4 Operating system: Red Hat Linux 3.2.3-47 Description:Signal 11 after concurrent inserts + updates Details: Hi, My postgresq