Hi,We're a team from Rome University (Italy) and we are working on an hacking of PostgreSQL MVCC. The basic idea is to have multiple instances of a same user transaction concurrently executing against the DB in order to achieve fault tolerance. We do not want to bother you with the details
letizia leo wrote:
and the doubt is the following: how is it possible that -line 144- Xmin
is the current transaction ( i.e. it has created this tuple, it is
holding an exclusive lock on it since it has not committed yet) and
that
-line 149- there is a different (?) transaction that is
On Tue, May 02, 2006 at 04:31:14PM +0200, letizia leo wrote:
snip
and the doubt is the following: how is it possible that -line 144- Xmin
is the current transaction ( i.e. it has created this tuple, it is
holding an exclusive lock on it since it has not committed yet) and
that
-line
