Hi, On 21 June 2017 at 13:11, Heikki Linnakangas <hlinn...@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 <https://mailtrack.io/> Sent with Mailtrack <https://mailtrack.io/install?source=signature&lang=en&referral=shubhambara...@gmail.com&idSignature=22>
Predicate-Locking-in-Gist-index_2.patch
Description: Binary data
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
