| From: | "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com> |
|---|---|
| To: | "Peter Koczan" <pjkoczan(at)gmail(dot)com> |
| Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Bus error in postgres 8.3 |
| Date: | 2008-04-29 06:03:23 |
| Message-ID: | 2e78013d0804282303s48be0a09m5b533bb3b0d0243@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Tue, Apr 29, 2008 at 10:35 AM, Peter Koczan <pjkoczan(at)gmail(dot)com> wrote:
>
> I'm going to try to force a crash on my test server to see if I can
> find out anything more. Does anyone know how to get useful debugging
> info at the time of the crash? I don't think I have things set to dump
> core anywhere, but that and/or stack traces would be nice (especially
> for child processes).
>
Yeah, a stack trace and if possible, a self contained test case to
reproduce the bug would help. If you are using a custom build, then
using a debug build would help a lot too.
Thanks,
Pavan
--
Pavan Deolasee
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | madhu.harchandani | 2008-04-29 06:10:07 | remove my name from mailing list |
| Previous Message | Tom Lane | 2008-04-29 06:01:04 | Re: Bus error in postgres 8.3 |