On Sun, Jan 8, 2012 at 9:25 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> I've taken that idea and used it to build a second Clog cache, known
> as ClogHistory which allows access to the read-only tail of pages in
> the clog. Once a page has been written to for the last time, it will
> be accessed via the ClogHistory Slru in preference to the normal Clog
> Slru. This separates historical accesses by readers from current write
> access by committers. Historical access doesn't force dirty writes,
> nor are commits made to wait when historical access occurs.

This seems to need a rebase.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

• CLOG contention, part 2 at 2012-01-08 14:25:40 from Simon Riggs

Responses

• Re: CLOG contention, part 2 at 2012-01-20 14:44:21 from Simon Riggs
• Re: CLOG contention, part 2 at 2012-01-20 15:16:42 from Simon Riggs

pgsql-hackers by date

Next:	From: Dimitri Fontaine	Date: 2012-01-20 13:52:25
	Subject: Re: Inline Extension
Previous:	From: Robert Haas	Date: 2012-01-20 13:32:46
	Subject: Re: Scaling XLog insertion (was Re: Moving more work outside WALInsertLock)