On Fri, 2008-12-19 at 10:52 +0000, Simon Riggs wrote:
> > You could
> > conservatively use OldestXmin as latestRemovedXid, but that could stall
> > the WAL redo a lot more than necessary. Or you could store
> > latestRemovedXid in the page header, but that would need to be
> > WAL-logged to ensure that it's valid after crash. Or you could look at
> > the heap to fetch the xmin/xmax, but that would be expensive.
>
> Agreed. Probably need to use OldestXmin then.
Just finished coding this up, plus TODO item to pin every index page.
Will post after some further testing.
Used RecentOldestXmin.
-- Simon Riggs www.2ndQuadrant.comPostgreSQL Training, Services and Support