From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Bernd Helmle <mailings(at)oopsware(dot)de>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: standalone backend PANICs during recovery |
Date: | 2016-04-06 01:50:17 |
Message-ID: | CA+TgmoZ07RD29ZThHoWuuM4KFWerx1NK6XUG+Skc7HOpvvd-nA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, Apr 2, 2016 at 5:57 PM, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
> Bernd Helmle wrote:
>> While investigating a problem on a streaming hot standby instance at a
>> customer site, i got the following when using a standalone backend:
>>
>> PANIC: btree_xlog_delete_get_latestRemovedXid: cannot operate with
>> inconsistent data
>> CONTEXT: xlog redo delete: index 1663/65588/65625; iblk 11, heap
>> 1663/65588/65613;
>>
>> The responsible PANIC is triggered here:
>>
>> src/backend/access/nbtree/nbtxlog.c:555
>>
>> btree_xlog_delete_get_latestRemovedXid(XLogReaderState *record)
>
> This PANIC was introduced in the commit below. AFAICS your proposed
> patch and rationale are correct.
If nobody's going to commit this right away, this should be added to
the next CommitFest so we don't forget it.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2016-04-06 01:52:13 | Re: pg_hba_lookup function to get all matching pg_hba.conf entries |
Previous Message | Robert Haas | 2016-04-06 01:47:43 | Re: Refactoring speculative insertion with unique indexes a little |