Thanks, Jeff.
Now I am going back to my old question.
Even though *Session 2* fails to update with UPDATE 0 message, its txid is
saved in xmax of updated(by *Session 1*) tuple.
As it becomes an old txid, how come new txids are able to view it?
-----
--
Thanks,
Rajan.
--
View this message in context: http://www.postgresql-archive.org/Re-have-trouble-understanding-xmin-and-xmax-with-update-operations-from-two-different-sessions-tp5969644p5969857.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.