Skip site navigation (1) Skip section navigation (2)

Re: Async Commit, v21 (now: v22)

From: "Simon Riggs" <simon(at)2ndquadrant(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-patches(at)postgresql(dot)org>
Subject: Re: Async Commit, v21 (now: v22)
Date: 2007-08-03 20:37:43
Message-ID: 1186173463.4136.27.camel@ebony.site (view raw or flat)
Thread:
Lists: pgsql-patches
On Wed, 2007-08-01 at 18:54 -0400, Tom Lane wrote:
> "Simon Riggs" <simon(at)2ndquadrant(dot)com> writes:
> > Here's v23, including all suggested changes, plus some reworking of the
> > transaction APIs to reduce the footprint of the patch. 
> 
> Applied with some editorialization ---

Thanks

>  I found a few bugs, as well as
> things that seemed they could be neater. 

Keen to improve: any chance of explaining, possibly offlist? 

>  Notable was that the patch
> would have significantly increased the contention for CLogControlLock by
> requiring two lock cycles to fetch a transaction's commit status and
> LSN.  I changed it so that TransactionIdGetStatus returns both pieces
> of information.

Thanks for picking that up.

-- 
  Simon Riggs
  EnterpriseDB  http://www.enterprisedb.com


In response to

pgsql-patches by date

Next:From: Decibel!Date: 2007-08-03 23:12:09
Subject: Re: Repair cosmetic damage (done by pg_indent?)
Previous:From: Tom LaneDate: 2007-08-03 19:34:35
Subject: Re: Correction of how to use TimeZone by ControlFile(xlog.c)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group