Re: [PATCHES] Lazy xid assignment V4 - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [PATCHES] Lazy xid assignment V4
Date
Msg-id 12856.1189054581@sss.pgh.pa.us
Whole thread Raw
In response to Re: [PATCHES] Lazy xid assignment V4  (Robert Treat <xzilla@users.sourceforge.net>)
List pgsql-hackers
Robert Treat <xzilla@users.sourceforge.net> writes:
> On Wednesday 05 September 2007 18:40, Tom Lane wrote:
>> 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.

Moving the goal posts, aren't we?  It was not possible to find that out
at all from the pg_locks view before.  (Well, you could guess based on
the type of table locks held, but you were only guessing.)

As of CVS HEAD you *can* determine that from pg_locks, to high
probability anyway, by looking to see which VXIDs have transaction IDs
locked.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Greg Smith
Date:
Subject: Just-in-time Background Writer Patch+Test Results
Next
From: Simon Riggs
Date:
Subject: Re: left outer join vs subplan