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

Re: Transaction Snapshot Cloning

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Gregory Stark <stark(at)enterprisedb(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Transaction Snapshot Cloning
Date: 2008-01-20 12:13:54
Message-ID: 1200831234.4255.476.camel@ebony.site (view raw or flat)
Thread:
Lists: pgsql-hackers
On Sat, 2008-01-12 at 18:46 +0000, Gregory Stark wrote:

> To do something like that the user would have to create a prepared transaction
> to save the snapshot. I think that makes sense though since effectively it's
> just requiring that the user explicitly do what would otherwise be a hidden
> implicit requirement -- that the user do something to hold globalxmin back to
> avoid having the snapshots expire.

This is a good idea which I will want to develop in the future, not yet
though.

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


In response to

Responses

pgsql-hackers by date

Next:From: Simon RiggsDate: 2008-01-20 12:16:02
Subject: Re: Transaction Snapshot Cloning
Previous:From: Teodor SigaevDate: 2008-01-20 09:57:17
Subject: Re: message string fixes

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