Re: Hot standby and b-tree killed items - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Hot standby and b-tree killed items
Date
Msg-id 1229710177.4793.567.camel@ebony.2ndQuadrant
Whole thread Raw
In response to Re: Hot standby and b-tree killed items  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
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



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Hot standby and b-tree killed items
Next
From: Martin Pihlak
Date:
Subject: Re: SQL/MED compatible connection manager