From: | Michael Holt <michael(at)aers(dot)ca> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Diagnosing Postgres Segfault |
Date: | 2010-11-30 00:21:27 |
Message-ID: | 9c40262b2d69c40bea6b744ceb8ec6f0@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Doesn't look like it at the moment. I'll see if we can get that setup and
go from there. Thanks.
-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Monday, November 29, 2010 4:10 PM
To: Michael Holt
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: [ADMIN] Diagnosing Postgres Segfault
Michael Holt <michael(at)aers(dot)ca> writes:
> I'm trying to figure out what might have caused this, partly because I
want
> to replicate the segfault to see if it is the cause of another system
> randomly freezing on us. Is there any way to figure out exactly what
query
> being run at the time of the crash was doing?
Is there a core dump file? If so, a stack trace from that might be
informative.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Anderson Valadares | 2010-11-30 00:42:37 | Re: failed to re-find parent key in index "22723655" for split pages 370836/370837 |
Previous Message | Tom Lane | 2010-11-30 00:09:41 | Re: Diagnosing Postgres Segfault |