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

Поиск
Список
Период
Сортировка
От Dong Yuan
Тема [GSoC] Question about "Explicitly support predicate locks in indexaccess methods besides btree"
Дата
Msg-id CAFbcfvRa6jf_tFwyicRu1awB7y3S2MGH8Yx53EHrUAVRxwDn_w@mail.gmail.com
обсуждение исходный текст
Ответы Re: [GSoC] Question about "Explicitly supportpredicate locks in index access methods besides btree"
Список 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

В списке pgsql-students по дате отправления:

Предыдущее
От: Dong Yuan
Дата:
Сообщение: [GSoC] Explicitly support predicate locks in index access methodsbesides btree
Следующее
От: Fabrízio de Royes Mello
Дата:
Сообщение: Re: [GSoC] Question about "Explicitly supportpredicate locks in index access methods besides btree"