| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Hot standby and b-tree killed items |
| Date: | 2008-12-19 18:09:37 |
| Message-ID: | 1229710177.4793.567.camel@ebony.2ndQuadrant |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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.com
PostgreSQL Training, Services and Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martin Pihlak | 2008-12-19 18:16:18 | Re: SQL/MED compatible connection manager |
| Previous Message | Simon Riggs | 2008-12-19 18:06:20 | Re: Hot standby and b-tree killed items |