Re: GSoC 2017 weekly progress reports ("Explicitly support predicate locks in index access methods besides b-tree")

From: Kevin Grittner <kgrittn(at)gmail(dot)com>
To: Shubham Barai <shubhambaraiss(at)gmail(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Andrew Borodin <amborodin86(at)gmail(dot)com>
Subject: Re: GSoC 2017 weekly progress reports ("Explicitly support predicate locks in index access methods besides b-tree")
Date: 2017-06-06 23:40:27
Message-ID: CACjxUsMKzcJKXA5oJk=oW0ue-n+8=oikf6TmWhgSq77DkAbpng@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jun 5, 2017 at 12:40 PM, Shubham Barai <shubhambaraiss(at)gmail(dot)com> wrote:

> GSoC (week 1)

> 4. went through source code of gist index to understand its implementation
>
> 5. found appropriate places in gist index AM to insert calls to existing
> functions (PredicateLockPage(), CheckForSerializableConflictIn() ...etc)

When you have a patch for any AM, please post it to the list. Each
AM will be reviewed and considered for commit separately.

--
Kevin Grittner
VMware vCenter Server
https://www.vmware.com/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2017-06-07 00:01:11 Re: PG10 transition tables, wCTEs and multiple operations on the same table
Previous Message Andres Freund 2017-06-06 23:20:57 Re: Error while creating subscription when server is running in single user mode