Re: [GENERAL] Re: have trouble understanding xmin and xmax withupdate operations from two different sessions - Mailing list pgsql-general

From Jeff Janes
Subject Re: [GENERAL] Re: have trouble understanding xmin and xmax withupdate operations from two different sessions
Date
Msg-id CAMkU=1zv-aDKyOJcsh5cu1bLSVVeDQCxKDMvPUN_q34N1QO7GQ@mail.gmail.com
Whole thread Raw
In response to [GENERAL] Re: have trouble understanding xmin and xmax with update operationsfrom two different sessions  (rajan <vgmonnet@gmail.com>)
List pgsql-general
On Mon, Jul 3, 2017 at 10:39 AM, rajan <vgmonnet@gmail.com> wrote:
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?

The database can see everything.  That is its job.  It constructs the principles of ACID out of non-ACID components.  But once you use pageinspect or select the system columns mxin and xmax, you start to peek through that illusion.
 
Cheers,

Jeff

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: [SPAM] Re: [SPAM] Re: [GENERAL] Invalid field size
Next
From: Moreno Andreo
Date:
Subject: Re: [SPAM] Re: [SPAM] Re: [GENERAL] Invalid field size