[GSoC] Question about "Explicitly support predicate locks in indexaccess methods besides btree" - Mailing list pgsql-hackers

From Dong Yuan
Subject [GSoC] Question about "Explicitly support predicate locks in indexaccess methods besides btree"
Date
Msg-id CAFbcfvRFYxjRRZGiERsoqG3+DrbsKyE65cie8wcDeURu7HikBA@mail.gmail.com
Whole thread Raw
List pgsql-hackers
Hi guys,

I'm confused about the this function, CheckForSerializableConflictOut(...). Can anyone help me out?

It seems like this function is used to check the rw-antidependencies out edge. This should be done when reading a written tuple. But btree does not call this function at all. The heapam used predicatelockpage(...)...

I use to think the in and out edge will be built when rw-antidependencies detected. CheckForSerializableConflictIn(...) can do this job. So CheckForSerializableConflictOut(...) function really confused me.

Best Wishes!
---
Dong

pgsql-hackers by date:

Previous
From: Fabien COELHO
Date:
Subject: Re: Variable substitution in psql backtick expansion
Next
From: Fabien COELHO
Date:
Subject: Re: Suggested fix for \p and \r in psql