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

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

From: Michael Fuhr <mike(at)fuhr(dot)org>
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-27 16:38:54
Message-ID: 20051027163854.GA23365@winnie.fuhr.org (view raw or flat)
Thread:
Lists: pgsql-bugs
[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 from the core dump.  Something like
this should work if you have gdb installed:

gdb /path/to/postgres /path/to/coredump

"/path/to/postgres" means the path to the executable file named
"postgres".  If you're not sure where that is then look in your
PostgreSQL startup script or use locate, find, etc.

gdb will print some startup info, then it'll present a "(gdb) "
prompt.  Type "bt" and hit Enter/Return ("bt" means backtrace)
(hopefully postgres was compiled with debugging symbols).  Copy the
output into an email message and post it here.  Use "q" to exit
gdb.  If Tom Lane gives differing or additional instructions then
listen to him, because he's one of the core developers.

-- 
Michael Fuhr

In response to

pgsql-bugs by date

Next:From: Mike GrantDate: 2005-10-27 20:45:05
Subject: Re: BUG #2000: psql does not prompt for password
Previous:From: IvanDate: 2005-10-27 14:45:54
Subject: Re: pg_dump bud with functions

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