From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jean-Luc Lachance <jllachan@nsd.ca>
Cc: pgsql-sql@postgresql.org
Cc: pgsql-general@postgresql.org
Subject: Re: Getting acces to MVCC version number
Date: Fri, 20 Sep 2002 17:23:32 -0400
Message-ID: <2566.1032557012@sss.pgh.pa.us> (raw)
In-Reply-To: <3D8B676D.3109ACFA@nsd.ca>
References: <200209201619.g8KGJ4J00624@candle.pha.pa.us>
<3D8B676D.3109ACFA@nsd.ca>
Jean-Luc Lachance <jllachan@nsd.ca> writes:
> How about making available the MVCC last version number just like oid is
> available. This would simplify a lot of table design. You know, having
> to add a field "updated::timestamp" to detect when a record was updated
> while viewing it (a la pgaccess).
> That way, if the version number do not match, one would know that the
> reccord was updated since last retrieved.
> What do think?
I think it's already there: see xmin and cmin. Depending on your needs,
testing xmin might be enough (you'd only need to pay attention to cmin
if you wanted to notice changes within your own transaction).
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, jllachan@nsd.ca, pgsql-general@postgresql.org
Subject: Re: Getting acces to MVCC version number
In-Reply-To: <2566.1032557012@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox