On Wednesday 05 September 2007 18:40, Tom Lane wrote:
> Robert Treat <xzilla@users.sourceforge.net> writes:
> > I'm trying to decide how reasonable the use case is. We have transactions
> > that run several hours long, often touching a number of tables, and I've
> > used the transaction to get a list of all of the relations a given
> > transaction is touching. This makes the above solution more annoying by
> > far, but I don't do it often, and I think I generally use the pid to get
> > that information anyway; if I used prepared transactions I'm sure I'd
> > feel stronger about this.
>
> I don't see why you wouldn't start using the VXID for this purpose?
>
I'm not sure either :-) Though, it would be nice to have an easy way to see
which transactions actually modified tables. Again, I not sure the use case
is reasonable, but it's there. If no one else feels strongly, let's document
a query to mimic the old column and move on.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
