Re: CLOG contention, part 2
От | Robert Haas |
---|---|
Тема | Re: CLOG contention, part 2 |
Дата | |
Msg-id | CA+TgmobEfHZE1LjcSaZcs0q_trfRLysg4Svk5JDuhtwQFGsDPA@mail.gmail.com обсуждение исходный текст |
Ответ на | CLOG contention, part 2 (Simon Riggs <simon@2ndQuadrant.com>) |
Ответы |
Re: CLOG contention, part 2
|
Список | pgsql-hackers |
On Fri, Jan 20, 2012 at 10:16 AM, Simon Riggs <simon@2ndquadrant.com> wrote: > On Fri, Jan 20, 2012 at 1:37 PM, Robert Haas <robertmhaas@gmail.com> wrote: >> 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. > > Still applies and compiles cleanly for me. D'oh. You're right. Looks like I accidentally tried to apply this to the 9.1 sources. Sigh... -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: