| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Geoffrey <esoteric(at)3times25(dot)net> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: trying to track down postgres deaths |
| Date: | 2007-06-11 22:29:38 |
| Message-ID: | 26634.1181600978@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Geoffrey <esoteric(at)3times25(dot)net> writes:
> Question is, when I see:
> #17 0x08151bc5 in ClosePostmasterPorts ()
> in the stack trace of the process, is this an indicator that the backend
> process was trying to shutdown?
No; that's a function that's executed immediately after fork() to close
postmaster sockets that the backend doesn't need to have open. It's
highly unlikely that you'd get a crash in there, and even more improbable
that it'd be 17 levels down the call stack. My bet is that you are
trying to debug with a non-debug-enabled build, and gdb is giving you a
less than accurate stack trace.
Rebuild with --enable-debug, and maybe also --enable-cassert, and see
what you can learn.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Geoffrey | 2007-06-11 22:51:31 | Re: trying to track down postgres deaths |
| Previous Message | lhaj.merigh@gmail.com | 2007-06-11 21:23:59 | Create a table B with data coming from table A |