Re: BUG #10432: failed to re-find parent key in index

From: Greg Stark <stark(at)mit(dot)edu>
To: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
Cc: Maciek Sakrejda <m(dot)sakrejda(at)gmail(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #10432: failed to re-find parent key in index
Date: 2014-06-02 17:17:46
Message-ID: CAM-w4HP=Fn2pV-GCc-C_b=gFXFnF+v-W-o+QV34YK63MSDNVfA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Ok, not sure why my first attempt didn't turn this up. I found the
split in segment 334/91:

rmgr: Btree len (rec/tot): 3776/ 9220, tx: 95765459, lsn:
334/91455AB8, prev 334/91455A70, bkp: 0100, desc: split_l: rel
1663/16385/1665279 left 175193, right 193740, next 182402, level 0,
firstright 138

I've attached all the xlog records pertaining to this relation
grepping for either of these two blocks.

Now interestingly the hot backup was taken starting at 334/90 and
replay didn't finish until 339/65 so it is entirely possible, even
likely, that the backup caught this split in an inconsistent state.

How should I go about dumping the two blocks? I have the backup prior
to WAL replay as well as all the WAL for this time period. I can't
connect to the database so I'm guessing this will look like replay
until it hits a record for these block, use dd to extract the block,
rinse lather repeat. Then dump each of those extracted pages using
pageinspect on byteas. This sounds pretty laborious :(

Attachment Content-Type Size
xlogdump.175193and193740 application/octet-stream 97.1 KB

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Nicolas Ross 2014-06-02 17:22:23 Re: BUG #10500: Cannot restore from a dump when some function is used in public shcema
Previous Message Andres Freund 2014-06-02 17:17:36 Re: BUG #10500: Cannot restore from a dump when some function is used in public shcema