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

Re: Nested transactions and tuple header info

From: Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>,Manfred Koizar <mkoi-pg(at)aon(dot)at>,David Blasby <dblasby(at)refractions(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Nested transactions and tuple header info
Date: 2004-06-02 15:47:33
Message-ID: 20040602154733.GA9227@dcc.uchile.cl (view raw or flat)
Thread:
Lists: pgsql-hackers
On Wed, Jun 02, 2004 at 11:12:31AM -0400, Tom Lane wrote:

> A global CID counter would also simplify other visibility tests.  Alvaro
> hasn't said anything about how he's doing visibility checks across
> different subxacts of the same main xact, but without global CID there
> would need to be some pretty ugly checks to determine whether a subxact
> happened before or after the CID cutoff your outer xact is interested
> in.

Yes, I'm using a global CID counter.

-- 
Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
"La vida es para el que se aventura"


In response to

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2004-06-02 16:23:37
Subject: Re: Nested transactions and tuple header info
Previous:From: Tom LaneDate: 2004-06-02 15:35:01
Subject: Re: ACLs versus ALTER OWNER

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