Re: [HACKERS] GSoC 2017 : Patch for predicate locking in Gist index

On 9 October 2017 at 18:57, Alexander Korotkov <a.korot...@postgrespro.ru> wrote: > On Thu, Oct 5, 2017 at 9:48 PM, Shubham Barai <shubhambara...@gmail.com> > wrote: > >> On 3 October 2017 at 00:32, Alexander Korotkov <a.korot...@postgrespro.ru >> > wrote

Re: [HACKERS] GSoC 2017 : Patch for predicate locking in Gist index

Sent with Mailtrack <#> On 3 October 2017 at 00:32, Alexander Korotkov wrote: >

Re: [HACKERS] GSoC 2017 : Patch for predicate locking in Gist index

On Sep 28, 2017 4:30 PM, "Alexander Korotkov" <a.korot...@postgrespro.ru> wrote: Hi! On Wed, Jun 21, 2017 at 10:52 AM, Shubham Barai <shubhambara...@gmail.com> wrote: > Hi, > > On 21 June 2017 at 13:11, Heikki Linnakangas <hlinn...@iki.fi> wrote: > >&g

Re: [HACKERS] GSoC 2017: weekly progress reports (week 6)

On 1 October 2017 at 01:47, Alexander Korotkov <a.korot...@postgrespro.ru> wrote: > On Sat, Sep 30, 2017 at 6:12 PM, Shubham Barai <shubhambara...@gmail.com> > wrote: > >> I have made changes according to your suggestions. Please have a look at >> the updated pat

Re: [HACKERS] GSoC 2017: weekly progress reports (week 6)

xander Korotkov < > a.korot...@postgrespro.ru> wrote: > >> On Wed, Aug 9, 2017 at 6:30 PM, Shubham Barai <shubhambara...@gmail.com> >> wrote: >> >>> Please find the updated patch for predicate locking in gin index here. >>> >>> There was a sma

Re: [HACKERS] GSoC 2017: weekly progress reports (week 4) and patch for hash index

Hi Thomas, I have attached the rebased version of patch here. Kind Regards, Shubham On 8 September 2017 at 06:37, Thomas Munro <thomas.mu...@enterprisedb.com> wrote: > Hi Shubham, > > On Tue, Jun 27, 2017 at 9:21 PM, Shubham Barai <shubhambara...@gmail.com> > wrote: &g

[HACKERS] GSoC 2017: weekly progress reports (week 9 and week 10)

Project: Explicitly support predicate locks in index AMs besides b-tree Hi, In the last two weeks, I mostly worked on predicate locking in rum index. Rum is based on gin access method. The main difference between rum and gin is that rum stores additional information in posting tree to perform a

Re: [HACKERS] GSoC 2017: weekly progress reports (week 6)

y 2017 at 19:08, Shubham Barai <shubhambara...@gmail.com> wrote: > Hi, > > I am attaching a patch for predicate locking in gin index. > > > Regards, > Shubham > > > > <https://mailtrack.io/> Sent with Mailtrack > <https://mailtrack.io/install?sourc

Re: [HACKERS] GSoC 2017: weekly progress reports (week 8)

Hi. I am attaching a patch for predicate locking in SP-Gist index Regards, Shubham <https://mailtrack.io/> Sent with Mailtrack <https://mailtrack.io/install?source=signature=en=shubhambara...@gmail.com=22> On 26 July 2017 at 20:50, Shubham Barai <shubhambara...@gmail.com>

[HACKERS] GSoC 2017: weekly progress reports (week 8)

Project: Explicitly support predicate locks in index AMs besides b-tree Hi, During this week, I worked on predicate locking in spgist index. I think, for spgist index, predicate lock only on leaf pages will be enough as spgist searches can determine if there is a match or not only at leaf level.

Re: [HACKERS] GSoC 2017: weekly progress reports (week 7)

mail.com> wrote: > On Tue, Jul 18, 2017 at 10:36 AM, Shubham Barai <shubhambara...@gmail.com> > wrote: > >> During this week, I read documentation and source code of BRIN index to >> understand its implementation. >> But later I found out that it is unlikely to imple

[HACKERS] GSoC 2017: weekly progress reports (week 7)

Project: Explicitly support predicate locks in index AMs besides b-tree Hi, During this week, I read documentation and source code of BRIN index to understand its implementation. But later I found out that it is unlikely to implement page level or tuple level predicate locking in BRIN index. In

Re: [HACKERS] GSoC 2017: weekly progress reports (week 6)

Hi, I am attaching a patch for predicate locking in gin index. Regards, Shubham <https://mailtrack.io/> Sent with Mailtrack <https://mailtrack.io/install?source=signature=en=shubhambara...@gmail.com=22> On 11 July 2017 at 19:10, Shubham Barai <shubhambara...@gmail.com>

[HACKERS] GSoC 2017: weekly progress reports (week 6)

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 enabled 2) created tests for different gin operators 3) went through some patches on commitfest to review 4)

[HACKERS] GSoC 2017: weekly progress reports (week 5) and Proposal for predicate locking in gin index

Project: Explicitly support predicate locks in index AMs besides b-tree Hi, During this week, I read documentation and source code of gin index to find appropriate places to insert calls to existing functions. Proposal Gin index consists of a Btree index over key values, where each key is an

[HACKERS] GSoC 2017: weekly progress reports (week 4) and patch for hash index

Project: Explicitly support predicate locks in index AMs besides b-tree Hi, During this week, I continued my work on predicate locking in the hash index and created a patch for it. As I have written in my proposal for the hash index, every scan operation acquires a predicate lock on the primary

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

Hi, On 22 June 2017 at 21:12, Alvaro Herrera <alvhe...@2ndquadrant.com> wrote: > Shubham Barai wrote: > > Hi, > > > > Now that hash index support write-ahead logging, it will be great if we > add > > support for predicate locking to it. > > Implementatio

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

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)

Re: [HACKERS] GSoC 2017 : Patch for predicate locking in Gist index

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 = di

Re: [HACKERS] GSoC 2017 weekly progress reports (week 3)

Hi , On 19 June 2017 at 22:49, Alvaro Herrera <alvhe...@2ndquadrant.com> wrote: > Shubham Barai wrote: > > Project: Explicitly support predicate locks in index AMs besides b-tree > > > > Hi, > > > > > > During this week, I continued my work on test

[HACKERS] GSoC 2017 weekly progress reports (week 3)

Project: Explicitly support predicate locks in index AMs besides b-tree Hi, During this week, I continued my work on testing and created my first patch for gist index. I have also started working on the hash index. In summary, I have done following things in this week. 1) updated tests to

Re: [HACKERS] GSoC 2017 : Patch for predicate locking in Gist index

Hi, Please find the updated patch here. Regards, Shubham On 16 June 2017 at 15:54, Shubham Barai <shubhambara...@gmail.com> wrote: > Hi, hackers! > > I have created my first patch for predicate locking in gist index. It > includes a test for verification of serialization f

[HACKERS] GSoC 2017 : Patch for predicate locking in Gist index

Hi, hackers! I have created my first patch for predicate locking in gist index. It includes a test for verification of serialization failures and a test to check false positives. I am submitting my patch little late because there were some issues with "make check" that I was trying to solve. Now,

Re: [HACKERS] GSoC 2017 weekly progress reports (week 2)

On 15 June 2017 at 07:23, Alvaro Herrera <alvhe...@2ndquadrant.com> wrote: > Shubham Barai wrote: > > Hi, > > > > I have made some changes in tests and pushed them to my branch. > > > > Thanks for helping me out with testing. > > > > Now, curre

Re: [HACKERS] GSoC 2017 weekly progress reports (week 2)

/2c02685a50a2b30654beb5c52542a57a46219c39 Regards, Shubham <https://mailtrack.io/> Sent with Mailtrack <https://mailtrack.io/install?source=signature=en=shubhambara...@gmail.com=22> On 13 June 2017 at 23:32, Andrew Borodin <boro...@octonica.com> wrote: > 2017-06-13 18:00 GMT+05:00 Shubh

[HACKERS] GSoC 2017 weekly progress reports (week 2)

Project: Explicitly support predicate locks in index AMs besides b-tree Hi, During this week, I mostly worked on testing to verify my code and on debugging to solve some issues I was having. I have specifically created two tests. The first test is about verifying serialization failure when there

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

GSoC (week 1) Hi, Here is the list of things I have done during this week. 1. read documentation on how to set up development environment 2. installed PostgreSQL on Ubuntu from source code 3. read documentation on gist index (http://www.sai.msu.su/~ megera/postgres/gist/) 4. went through

Re: [HACKERS] GSoC 2017 : Proposal for predicate locking in gist index

Hi, Kevin sir! On 1 June 2017 at 02:20, Kevin Grittner <kgri...@gmail.com> wrote: > On Wed, May 31, 2017 at 3:02 PM, Shubham Barai <shubhambara...@gmail.com> > wrote: > > > I have been accepted as GSoC student for the project "Explicitly support > > p

[HACKERS] GSoC 2017 : Proposal for predicate locking in gist index

Hello everyone, I have been accepted as GSoC student for the project "Explicitly support predicate locks in index access methods besides b-tree". I want to share my approach for implementation of page level predicate locking in gist index. Any suggestions will be appreciated. Proposal The

[HACKERS] GSoC 2017 Proposal for "Explicitly support predicate locks in index access methods besides btree"

Hi guys, My name is Shubham Barai and I am a final year student at Maharashtra Institute of Technology, Pune, India. I am very interested in contributing Postgresql this year through GSoC project. I am particularly interested in working on the project "Explicitly support predicate locks in

[HACKERS] about google summer of code 2016

? Thanks, Shubham Barai

[HACKERS] Optimization- Check the set of conditionals on a WHERE clause against CHECK constraints.

Hello hackers, I was searching for project ideas and found this 1.Optimization- Check the set of conditionals on a WHERE clause against CHECK constraints on the table being queried and remove any conditionals which *must* be true due to the CHECK constraints. Is it expensive for simple

[HACKERS] UNIQUE capability to hash indexes

Hello hackers , I wanted to know if anyone is working on these projects from todo list. 1.Add UNIQUE capability to hash indexes 2.Allow multi-column hash indexes I couldn't find any discussion about these projects. Thanks, Shubham Barai