Tom Lane wrote:
> Heikki Linnakangas <heikki(at)enterprisedb(dot)com> writes:
>> While looking at the HOT patch, I noticed that if there's an index tuple
>> pointing to a non-existing heap tuple, we just silently ignore it.
>
> This is intentional --- consider case where VACUUM has removed both
> index and heap entries while some other (amazingly slow...) process is
> in flight from the index to the heap.
Hmm. In b-tree we keep the index page pinned while we do the heap fetch
to avoid that, but apparently we don't have that interlock in other
indexams.
Ok, never mind.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com