Re: Row versioning

From: "Ruediger Herrmann" <ruediger(dot)herrmann(at)gmx(dot)de>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Row versioning
Date: 2004-10-22 13:16:22
Message-ID: 16272.1098450982@www37.gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


thanks for your replay. This approach sounds very comfy. As I read the
documentation this is kind of a "transaction sequence" or better a
"unique transaction id". Am I right with this? So every row inserted or
updated within the same transaction is tagged with the same xmin.

Is there any information wether this approach is future proof? I heard
the OID is depecated now, maybe XMIN is next, no idea...

TIA
Ruediger

> > has anyone implemented row versions/timestamps in
> PostgreSQL or any
> > thoughts on this?
> > Did I hit the right term? What I want to achieve
> is optimistic
> > concurrency beyound transaction boundaries. When
> retrieving data
> > I would also retrieve the row version and later
> on, in a different
> > transaction, before updating the data, I could
> check if was unchanged.
>
> You could use the xmin system column for this.
>
> regards, tom lane
>
>
>

--
Geschenkt: 3 Monate GMX ProMail + 3 Ausgaben der TV Movie mit DVD
++++ Jetzt anmelden und testen http://www.gmx.net/de/go/mail ++++

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jan Wieck 2004-10-22 13:26:49 Re: Slony-I 1.0.4 Released
Previous Message John Wells 2004-10-22 12:52:28 PostgreSQL-related job posting