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

Re: Transaction Snapshot Cloning

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Chris Browne <cbbrowne(at)acm(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Transaction Snapshot Cloning
Date: 2008-03-28 18:58:14
Message-ID: 1206730694.4285.1771.camel@ebony.site (view raw or flat)
Thread:
Lists: pgsql-hackers
On Fri, 2008-03-28 at 11:33 -0400, Chris Browne wrote:
> bruce(at)momjian(dot)us (Bruce Momjian) writes:
> > Added to TODO:
> >
> > * Allow one transaction to see tuples using the snapshot of another
> >   transaction
> >
> >   This would assist multiple backends in working together.
> >   http://archives.postgresql.org/pgsql-hackers/2008-01/msg00400.php
> 
> FYI, code for this is presently available on pgFoundry, at:
>    <http://pgfoundry.org/projects/snapclone/>.
> 
> I have some benchmarking scripts to commit to it, once I get added to
> the project. (Simon?  :-))
> 
> FYI, preliminary testing, on a machine hooked up to an EMC CX700 disk
> array is showing that, if I do concurrent dumps of 4 tables, it gives
> a bit better than a 2x speedup over dumping the four tables serially,
> so there's definitely some fruit here.

Oh, very cool. Thanks for testing. 

I'll add you now - must have missed that, sorry.

My view is that the TODO item is still needed because we want to work
this into the backend more fully.

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

  PostgreSQL UK 2008 Conference: http://www.postgresql.org.uk


In response to

pgsql-hackers by date

Next:From: Simon RiggsDate: 2008-03-28 19:09:59
Subject: Re: [PATCHES] Implemented current_query
Previous:From: Martijn van OosterhoutDate: 2008-03-28 18:48:47
Subject: Re: Commitfest patches

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