Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> wrote:
> Predicate locks on indexes are only needed to lock key ranges, to
> notice later insertions into the range, right? For locks on tuples
> that do exist, we have locks on the heap. If we're just about to
> delete every tuple in the heap, that doesn't need to conflict with
> any locks on indexes, because we're deleting, not inserting. So I
> don't think we need to care about index locks here at all, only
> locks on the heap. Am I missing something?
You're right again. My brain must be turning to mush. This
function can also become simpler, and there is now no reason at all
to add catalog cache lookups to predicate.c. I think that leaves me
with all the answers I need to get a new patch out this evening
(U.S. Central Time).
Thanks,
-Kevin
