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

Re: Transaction Snapshot Cloning

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Transaction Snapshot Cloning
Date: 2008-01-11 20:42:42
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Fri, 2008-01-11 at 20:39 +0000, Simon Riggs wrote:
> On Fri, 2008-01-11 at 15:05 -0500, Tom Lane wrote:
> Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> > > If we had a function 
> > > 	replace_serializable_snapshot(master_xid, txid_snapshot)
> > > this would allow us to use the txid_snapshot values to replace our
> > > transaction's serializable snapshot.
> > 
> > ... whereupon we'd get wrong answers.  Certainly you could not allow
> > transaction xmin to go backwards, and I'm not sure what other
> > restrictions there would be, but the whole thing gives me the willies.

Sorry, forgot to add
- global xmin isn't going backwards
- neither is latest completed xid

The xmin of the transaction will go backwards, but as long as we don't
do anything prior to the setting of the cloned snapshot, what can go
wrong? :-)

  Simon Riggs

In response to


pgsql-hackers by date

Next:From: Gokulakannan SomasundaramDate: 2008-01-11 21:10:17
Subject: Re: Some ideas about Vacuum
Previous:From: Simon RiggsDate: 2008-01-11 20:39:04
Subject: Re: Transaction Snapshot Cloning

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