Re: CLOG contention, part 2 - Mailing list pgsql-hackers

From Robert Haas
Subject Re: CLOG contention, part 2
Date
Msg-id CA+Tgmoa-+UThwitSYkn6tnpBCoHksaHPQqG=Z3oA9fg9HoXQvQ@mail.gmail.com
Whole thread Raw
In response to CLOG contention, part 2  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: CLOG contention, part 2
Re: CLOG contention, part 2
List pgsql-hackers
On Sun, Jan 8, 2012 at 9:25 AM, Simon Riggs <simon@2ndquadrant.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


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Scaling XLog insertion (was Re: Moving more work outside WALInsertLock)
Next
From: Dimitri Fontaine
Date:
Subject: Re: Inline Extension