Re: GSoC 2017: weekly progress reports (week 7)

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Shubham Barai <shubhambaraiss(at)gmail(dot)com>
Cc: Andrew Borodin <amborodin86(at)gmail(dot)com>, Kevin Grittner <kgrittn(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: GSoC 2017: weekly progress reports (week 7)
Date: 2017-07-20 15:48:00
Message-ID: CA+TgmoaDtzTC02gx2E_w1mh7eAaaJ_ONJadu0AQGUrgSMou8Kw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jul 18, 2017 at 10:36 AM, Shubham Barai <shubhambaraiss(at)gmail(dot)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 implement page level or tuple
> level predicate locking in BRIN index.
> In this week, I also fixed a small issue and updated my previous patch for
> gin index. Currently, I am working on
> sp-gist index.
>

It's a shame that nobody seems to be answering emails like this, but you
also haven't provided much detail here - e.g. *why* is BRIN unlikely to
work out well? I think I know the answer, but it'd be good to spell out
your thoughts on the subject, I think.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2017-07-20 15:51:55 Re: Increase Vacuum ring buffer.
Previous Message Dmitry Dolgov 2017-07-20 15:41:51 Re: JSONB - JSONB operator feature request