Postgres Pro
Downloads
Home   >   mailing lists

Thread: [GSoC] Question about "Explicitly support predicate locks in indexaccess methods besides btree"

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

From
Dong Yuan
Date:
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

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

From
Fabrízio de Royes Mello
Date:

Em dom, 2 de abr de 2017 às 05:16, Dong Yuan <doffery20@gmail.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