Re: [HACKERS] GSoC 2017: weekly progress reports (week 6)
От | Shubham Barai |
---|---|
Тема | Re: [HACKERS] GSoC 2017: weekly progress reports (week 6) |
Дата | |
Msg-id | CALxAEPu4SqRT8=6RE8rOspgbTrJu+rgNeJ8=zE00K1Lz6Vnfdw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] GSoC 2017: weekly progress reports (week 6) (Shubham Barai <shubhambaraiss@gmail.com>) |
Ответы |
Re: [HACKERS] GSoC 2017: weekly progress reports (week 6)
|
Список | pgsql-hackers |

Hi,
There was a small issue in the previous patch. I didn't consider the case
where only root page exists in the tree, and there is a predicate lock on it,
and it gets split.
If we treat the original page as a left page and create a new root and right
If we treat the original page as a left page and create a new root and right
page, then we just need to copy a predicate lock from the left to the right
page (this is the case in B-tree).
But if we treat the original page as a root and create a new left and right
page, then we need to copy a predicate lock on both new pages (in the case of rum and gin).
link to updated code and tests: https://github.com/shubhambaraiss/postgres/commit/6172639a104785f051cb4aa0d511c58f2bae65a6
Regards,
Shubham
On 17 July 2017 at 19:08, Shubham Barai <shubhambaraiss@gmail.com> wrote:
On 11 July 2017 at 19:10, Shubham Barai <shubhambaraiss@gmail.com> wrote:Project: Explicitly support predicate locks in index AMs besides b-tree
I have done following tasks during this week.1) worked on how to detect rw conflicts when fast update is enabled2) created tests for different gin operators3) went through some patches on commitfest to review4) solved some issues that came up while testinglink to the code: https://github.com/shubhambaraiss/postgres/commit/1365 d75db36a4e398406dd266c3d4fe8e1 ec30ff
Вложения
В списке pgsql-hackers по дате отправления: