On 2013-07-31 01:27:39 +0000, mac...@heroku.com wrote: > The following bug has been logged on the website: > > Bug reference: 8347 > Logged by: Maciek Sakrejda > Email address: mac...@heroku.com > PostgreSQL version: 9.2.4 > Operating system: Ubuntu 12.04.2 LTS 64-bit > Description: > > Running into a recovery failure on a customer's replica: > > > Jul 31 00:11:55: LOG: restored log file "00000001000000E200000067" from > archive > Jul 31 00:11:55: WARNING: will not overwrite a used ItemId > Jul 31 00:11:55: CONTEXT: xlog redo insert: rel 1663/16385/16619; tid > 25260/37 > Jul 31 00:11:55: PANIC: heap_insert_redo: failed to add tuple > Jul 31 00:11:55: CONTEXT: xlog redo insert: rel 1663/16385/16619; tid > 25260/37 > > > I see a similar bug filed [1], but no replies. This happens repeatedly when > attempting to apply this segment.
Any chance you could https://github.com/snaga/xlogdump that and the neighbouring segments? That might tell us whether we're dealing with broken locking or possibly disk corruption (doesn't sound too likely). Just to be sure, you're not running with full_page_writes = off or something? Could you possibly run a patched postgres against that, to get more info? Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
