"Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com> writes:
> So are you suggesting we go back to the earlier way of handling
> aborted tuples separately ? But then we can not do that by simply
> checking for !HeaptupleIsHotUpdated. There could be several aborted
> tuples at the end of the chain of which all but one are marked HotUpdated.
> Or are you suggesting we also check for XMIN_INVALID for detecting
> aborted tuples ?
Yeah. As the code stands, anything that's XMIN_INVALID will be
considered not-HotUpdated (look at the macro...). So far I've seen no
place where there is any value in following a HOT chain past such a
tuple --- do you see any? Every descendant tuple must be XMIN_INVALID
as well ...
regards, tom lane
In response to
pgsql-patches by date
|Next:||From: Andrew Dunstan||Date: 2007-09-17 00:40:47|
|Subject: Re: invalidly encoded strings|
|Previous:||From: Pavan Deolasee||Date: 2007-09-16 18:42:23|
|Subject: Re: HOT synced with HEAD|