[GSoC] Question about "Explicitly support predicate locks in index access methods besides btree"

From: Dong Yuan <doffery20(at)gmail(dot)com>
To: pgsql-students(at)postgresql(dot)org
Subject: [GSoC] Question about "Explicitly support predicate locks in index access methods besides btree"
Date: 2017-04-02 08:16:09
Message-ID: CAFbcfvRa6jf_tFwyicRu1awB7y3S2MGH8Yx53EHrUAVRxwDn_w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-students

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

Responses

Browse pgsql-students by date

  From Date Subject
Next Message Fabrízio de Royes Mello 2017-04-02 14:20:57 Re: [GSoC] Question about "Explicitly support predicate locks in index access methods besides btree"
Previous Message Arseny Sher 2017-04-01 21:13:15 Re: [GSoC] Push-based query executor discussion