From: | Bernd Helmle <mailings(at)oopsware(dot)de> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: standalone backend PANICs during recovery |
Date: | 2016-09-16 08:43:32 |
Message-ID: | F4AE3565D7D8132348A753CC@eje.land.credativ.lan |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
--On 3. September 2016 um 02:05:00 -0400 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Well, the "use case" was a crashed hot standby at a customer site (it
>> kept PANICing after restarting), where i decided to have a look through
>> the recovery process with gdb. The exact PANIC was
>
>> 2016-03-29 15:12:40 CEST [16097]: [26-1] user=,db=,xid=0,vxid=1/0 FATAL:
>> unexpected GIN leaf action: 0
>
> BTW, that didn't happen to be on big-endian hardware did it?
You're right, this was RHEL7 on a POWER7 machine.
--
Thanks
Bernd
From | Date | Subject | |
---|---|---|---|
Next Message | Ashutosh Bapat | 2016-09-16 08:56:17 | Re: Printing bitmap objects in the debugger |
Previous Message | Kyotaro HORIGUCHI | 2016-09-16 08:31:30 | Re: IF (NOT) EXISTS in psql-completion |