On 2/20/07, Bruce Momjian <[EMAIL PROTECTED]> wrote:
Pavan Deolasee wrote:
> When following a HOT-update chain from the index fetch, if we notice
> the root tuple is dead and it is HOT-updated, we try to prune the chain
> the smallest possible length. To do that, the share lock is upgraded to
> exclusive lock and the tuple chain is followed till we find a
> tuple. At that point, the root t_ctid is made point to that tuple. In
I assume you meant recently-dead here, rather than live/recently-dead,
because we aren't going to change live ctids, right?
No, I meant live or recently-dead (in fact, anything other than
We are not changing the tids here, but only pruning the HOT-update chain.
After pruning, the root->t_ctid points to the oldest tuple that might be
visible to any backend. The live tuples are still identified by their
original tid and index reachable from the root tuple.