On Sat, Apr 2, 2016 at 5:57 PM, Alvaro Herrera <alvhe...@2ndquadrant.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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
