Re: [HACKERS] GSoC 2017 : Patch for predicate locking in Gist index - Mailing list pgsql-hackers

From Shubham Barai
Subject Re: [HACKERS] GSoC 2017 : Patch for predicate locking in Gist index
Date
Msg-id CALxAEPt8REhBJA-zgQWorGKWqUqqCchxO-RyK06PJgSJmZYKbg@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] GSoC 2017 : Patch for predicate locking in Gist index  (Heikki Linnakangas <hlinnaka@iki.fi>)
Responses Re: [HACKERS] GSoC 2017 : Patch for predicate locking in Gist index  (Andrey Borodin <x4mmm@yandex-team.ru>)
Re: [HACKERS] GSoC 2017 : Patch for predicate locking in Gist index  (Alexander Korotkov <a.korotkov@postgrespro.ru>)
List pgsql-hackers
Hi,

On 21 June 2017 at 13:11, Heikki Linnakangas <hlinnaka@iki.fi> wrote:
On 06/16/2017 01:24 PM, Shubham Barai wrote:
@@ -497,6 +499,13 @@ gistplacetopage(Relation rel, Size freespace, GISTSTATE *giststate,
                        for (ptr = dist->next; ptr; ptr = ptr->next)
                                UnlockReleaseBuffer(ptr->buffer);
                }
+
+               for (ptr = dist; ptr; ptr = ptr->next)
+                       PredicateLockPageSplit(rel,
+                                               BufferGetBlockNumber(buffer),
+                                               BufferGetBlockNumber(ptr->buffer));
+
+

I think this new code needs to go before the UnlockReleaseBuffer() calls above. Calling BufferGetBlockNumber() on an already-released buffer is not cool.

- Heikki

I know that. This is the old version of the patch. I had sent updated patch later. Please have a look at updated patch.

Regards,
Shubham



Sent with Mailtrack
Attachment

pgsql-hackers by date:

Previous
From: Mahendranath Gurram
Date:
Subject: Re: [HACKERS] Regarding Postgres Dynamic Shared Memory (DSA)
Next
From: jasrajd
Date:
Subject: Re: [HACKERS] An attempt to reduce WALWriteLock contention