| From: | "Ruediger Herrmann" <ruediger(dot)herrmann(at)gmx(dot)de> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Row versioning |
| Date: | 2004-10-21 22:27:34 |
| Message-ID: | 11331.1098397654@www51.gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi all,
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.
(row version at read time = row version at update time)
What are the pro's and con's about adding a "sequence" row that is
incremented by a trigger each time the row is updated?
Is having a timestamp row instand better?
Regards
Ruediger
--
Geschenkt: 3 Monate GMX ProMail + 3 Ausgaben der TV Movie mit DVD
++++ Jetzt anmelden und testen http://www.gmx.net/de/go/mail ++++
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gaetano Mendola | 2004-10-21 22:32:41 | Re: Slony-I 1.0.4 Released |
| Previous Message | Gaetano Mendola | 2004-10-21 22:03:46 | Re: table size/record limit |