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: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Manfred Koizar <mkoi-pg(at)aon(dot)at>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>,David Blasby <dblasby(at)refractions(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Nested transactions and tuple header info
Date: 2004-06-01 22:55:39
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Tue, Jun 01, 2004 at 06:40:07PM -0400, Bruce Momjian wrote:

> So, we need a way to record the xmin and xmax while keeping cmin and
> cmax in the tuple header.  My idea is for subtransactions to create
> additional xid's that represent the opposite of the commit state for
> changing tuples created by earlier subtransactions.

Hmm, interesting idea.  What seems more interesting is that the change
seems to be confined to HeapTupleHeaderSetXmax.  Every transaction and
subtransaction will need two Xids (I think we can even optimize it so
the "abort xid" is taken only as needed).

I don't see anything immediately that would invalidate this idea.  I'll
marinate it while I write the trigger stuff, and wait for other
comments.  If nothing bad arises I'll try an implementation and report


Alvaro Herrera (<alvherre[a]>)
"Nunca confiaré en un traidor.  Ni siquiera si el traidor lo he creado yo"
(Barón Vladimir Harkonnen)

In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2004-06-01 23:28:59
Subject: Re: Nested transactions and tuple header info
Previous:From: Bruce MomjianDate: 2004-06-01 22:40:07
Subject: Nested transactions and tuple header info

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