Re: SSI bug?

Looking at the prior/next version chaining, aside from the looping 
issue, isn't it broken by lock promotion too? There's a check in 
RemoveTargetIfNoLongerUsed() so that we don't release a lock target if 
its priorVersionOfRow is set, but what if the tuple lock is promoted to 
a page level lock first, and PredicateLockTupleRowVersionLink() is 
called only after that? Or can that not happen because of something else 
that I'm missing?

--   Heikki Linnakangas  EnterpriseDB   http://www.enterprisedb.com