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

From: Greg Stark <stark(at)mit(dot)edu>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Maciek Sakrejda <m(dot)sakrejda(at)gmail(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-04 11:26:17
Message-ID: CAM-w4HOZ8QFaYVwkFxb68EOQ_JZ6uh_+OzOrNSmEAuoV3OVR6Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Jun 4, 2014 at 12:14 PM, Greg Stark <stark(at)mit(dot)edu> wrote:
> Because it had noticed the incomplete
> split it had skipped every restartpoint and the next time I tried to
> start it it insisted on restarting recovery from the beginning.

Incidentally this also caused operational problems. Suppressing all
restartpoints also meant Postgres kept around all the WAL from the
entire recovery. This caused the pg_xlog volume to fill up.

--
greg

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Andres Freund 2014-06-04 11:35:19 Re: BUG #10432: failed to re-find parent key in index
Previous Message gnuplanet 2014-06-04 11:16:50 BUG #10526: bad sequence rename