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

Re: Release Notes Overview

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Gregory Stark <stark(at)enterprisedb(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Release Notes Overview
Date: 2007-10-05 17:18:23
Message-ID: 1191604703.4223.401.camel@ebony.site (view raw or flat)
Thread:
Lists: pgsql-hackers
On Fri, 2007-10-05 at 11:24 +0100, Gregory Stark wrote:
> "Simon Riggs" <simon(at)2ndquadrant(dot)com> writes:
> 
> > Asynchronous Commit allows some transactions to commit faster than
> > others, offering a trade-off between performance and durability for
> > specific transaction types only
> 
> A lot of users will be confused about what asynchronous commit does. I think
> it's important to be consistently precise when describing it. 
> 
> It doesn't allow commits to be any faster, what it does is "allow clients to
> start a new transaction and continue working without waiting for their
> previous commit to complete". Saying something like "This allows high volumes
> of short transactions such as typical web sites to run more efficiently and
> with fewer connections" might also help clarify the use case it helps.

The general shape of the overview was what I was looking at. 

I agree with your specific comment.

-- 
  Simon Riggs
  2ndQuadrant  http://www.2ndQuadrant.com


In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2007-10-05 17:18:54
Subject: Re: Polymorphic arguments and composite types
Previous:From: Simon RiggsDate: 2007-10-05 17:14:45
Subject: Re: Polymorphic arguments and composite types

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