Postgres Pro
Downloads
Home   >   mailing lists

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

From Dong Yuan
Subject [GSoC] Question about "Explicitly support predicate locks in indexaccess methods besides btree"
Date
Msg-id CAFbcfvRa6jf_tFwyicRu1awB7y3S2MGH8Yx53EHrUAVRxwDn_w@mail.gmail.com
Whole thread Raw
Responses Re: [GSoC] Question about "Explicitly supportpredicate locks in index access methods besides btree"  (Fabrízio de Royes Mello <fabriziomello@gmail.com>)
List pgsql-students
Tree view
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 should be built when rw-antidependencies detected. CheckForSerializableConflictIn(...) can do this job. So CheckForSerializableConflictOut(...) function really confused me.

Best Wishes!
---
Dong

pgsql-students by date:

Previous
From: Dong Yuan
Date:
Subject: [GSoC] Explicitly support predicate locks in index access methodsbesides btree
Next
From: Fabrízio de Royes Mello
Date:
Subject: Re: [GSoC] Question about "Explicitly supportpredicate locks in index access methods besides btree"