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

From: Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com>
To: Dong Yuan <doffery20(at)gmail(dot)com>, pgsql-students(at)postgresql(dot)org
Subject: Re: [GSoC] Question about "Explicitly support predicate locks in index access methods besides btree"
Date: 2017-04-02 14:20:57
Message-ID: CAFcNs+pk8p4R1TVakNz2XRazKeeHmAeiD80VJ2=5bh9MesrNoA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-students

Em dom, 2 de abr de 2017 às 05:16, Dong Yuan <doffery20(at)gmail(dot)com> escreveu:

> 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.
>
>
This mailing list isn't the best place for your question. Please send it to
pgsql-hackers instead.

Regards,

--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: http://www.timbira.com.br
>> Blog: http://fabriziomello.github.io
>> Linkedin: http://br.linkedin.com/in/fabriziomello
>> Twitter: http://twitter.com/fabriziomello
>> Github: http://github.com/fabriziomello

In response to

Browse pgsql-students by date

  From Date Subject
Next Message Alexander Korotkov 2017-04-06 13:11:23 Re: [GSoC] Push-based query executor discussion
Previous Message Dong Yuan 2017-04-02 08:16:09 [GSoC] Question about "Explicitly support predicate locks in index access methods besides btree"