[HACKERS] GSoC 2017 Proposal for predicate locking in hash index

Поиск
Список
Период
Сортировка
От Shubham Barai
Тема [HACKERS] GSoC 2017 Proposal for predicate locking in hash index
Дата
Msg-id CALxAEPuj=71G22ohMLsWoHjhTKWnhsVdqg0X0tySr3sQXpXFNg@mail.gmail.com
обсуждение исходный текст
Ответы Re: [HACKERS] GSoC 2017 Proposal for predicate locking in hash index  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Список pgsql-hackers
Дерево обсуждения
Hi, 

Now that hash index support write-ahead logging, it will be great if we add support for predicate locking to it. 
Implementation of predicate locking in hash index seems very simple.
I have already made changes in the code. I am currently working on testing.

Here is my approach 

1) PredicateLockPage()

->_hash_first()

During a scan operation, acquire a predicate lock on the primary page of a bucket.

2) CheckForSerializableConflictIn()

->_hash_doinsert()

During an insert operation, check if there is any predicate lock on the primary page of a bucket.


3) PredicateLockPageSplit()

In case of a bucket split, copy predicate lock from the primary page of an old bucket to the primary page of a new bucket.

Any suggestions or corrections will be appreciated.

Regards,
Shubham



Sent with Mailtrack

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

Предыдущее
От: Peter Eisentraut
Дата:
Сообщение: Re: [HACKERS] Logical replication: stuck spinlock atReplicationSlotRelease
Следующее
От: Robert Haas
Дата:
Сообщение: Re: [HACKERS] Adding connection id in the startup message