"Ruediger Herrmann" <[EMAIL PROTECTED]> writes:
> Is there any information wether this approach is future proof?
[ shrug... ] As much as anything that's not specified by the SQL
standard is around here. We have no plans to replace MVCC, and
xmin/xmax are a pretty fundamental part of that.
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 informat
"Ruediger Herrmann" <[EMAIL PROTECTED]> writes:
> 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
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
transact
