From: | Kelly Burkhart <kelly(dot)burkhart(at)gmail(dot)com> |
---|---|
To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Backend Crash v8.4.2 |
Date: | 2010-06-29 14:17:25 |
Message-ID: | AANLkTila2oqHFrzThP3dA9sBwI4BxsKo5cZVKNC8lz7S@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hello,
We had a backend crash this morning. Version is PostgreSQL 8.4.2
running on openSuSE 11.2. This machine is connected via iSCSI to a
Dell Equallogic array. We've been running 8.4.2 since February (I
believe) without issue, although we've recently upgraded this machine
from 24G to 72G RAM. I don't see anything alarming in
/var/log/messages, the line from the crash:
2010-06-29T07:59:07.912030-05:00 db01-primary kernel: [839991.262273]
postmaster[11109]: segfault at 10f ip 000000000068d884 sp
00007fff78fa9dc0 error 4 in postgres[400000+44b000]
The crash left a core file, does the stack trace indicate anything crucial?
(gdb) where
#0 0x000000000068d884 in SearchCatCacheList ()
#1 0x0000000100000000 in ?? ()
#2 0x0000000000bbcbe0 in ?? ()
#3 0x00007f3b3a86a580 in ?? ()
#4 0x72ddbea20068dae0 in ?? ()
#5 0x00007fff78faa720 in ?? ()
#6 0x0000000000000000 in ?? ()
Current language: auto
The current source language is "auto; currently asm".
Can anyone provide some guidance on how I can go about discovering the
cause? There are some indications in the 8.4.3 and 8.4.4 release
notes that some possible crashes are fixed. Do those issues
correspond with the stack trace above?
Thanks in advance for any advice,
-Kelly
From | Date | Subject | |
---|---|---|---|
Next Message | erobles | 2010-06-29 14:22:56 | Fwd: Re: Weird trouble with select |
Previous Message | Joshua Tolley | 2010-06-29 13:59:02 | Re: Weird trouble with select |