Re: [HACKERS] Tuple hint bits (INFOMASK) upon transaction abort

2006-06-15 Thread Qingqing Zhou
"letizia leo" <[EMAIL PROTECTED]> wrote > > Transaction T1 updates a given tuple -- xmax is set to T1 on that tuple > ... > later on, T1 aborts... we believe that in this circumstance HEAP_XMAX_INVALID should > be set on the tuple to signal that the tuple was not actually "deleted" by T1 since

Re: [HACKERS] Tuple hint bits (INFOMASK) upon transaction abort

2006-06-15 Thread Tom Lane
letizia leo <[EMAIL PROTECTED]> writes: > Transaction T1 updates a given tuple -- xmax is set to T1 on that tuple > ... > later on, T1 aborts... we believe that in this circumstance > HEAP_XMAX_INVALID should be set on the tuple to signal that the tuple was not > actually "deleted" by T1 since

[HACKERS] Tuple hint bits (INFOMASK) upon transaction abort

2006-06-15 Thread letizia leo
I am studying the postgresql kernel and the following question arose... I hope somebody out there can help me find the answers to my doubts. Scenario: Transaction T1 updates a given tuple -- xmax is set to T1 on that tuple ... later on, T1 aborts... we believe that in this circumstance HEAP_XMAX_