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

From: Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>
To: Shubham Barai <shubhambaraiss(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Andrew Borodin <amborodin86(at)gmail(dot)com>, Kevin Grittner <kgrittn(at)gmail(dot)com>
Subject: Re: GSoC 2017: weekly progress reports (week 6)
Date: 2017-10-02 16:51:03
Message-ID: CAPpHfduns_j0jn2VGXvwDLP31dUXYU=3WCC31DzkG_Qe5WDFbQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-www

On Sun, Oct 1, 2017 at 11:53 AM, Shubham Barai <shubhambaraiss(at)gmail(dot)com>
wrote:

> Yes, page-level predicate locking should happen only when fast update is
> off.
> Actually, I forgot to put conditions in updated patch. Does everything
> else look ok ?
>

I think that isolation tests should be improved. It doesn't seems that any
posting tree would be generated by the tests that you've provided, because
all the TIDs could fit the single posting list. Note, that you can get
some insight into GIN physical structure using pageinspect contrib.

------
Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Petr Jelinek 2017-10-02 16:59:41 Re: Issues with logical replication
Previous Message Adam Brusselback 2017-10-02 16:50:14 Re: generated columns

Browse pgsql-www by date

  From Date Subject
Next Message Gabriel 2017-10-04 12:42:42 editor privileges
Previous Message Magnus Hagander 2017-10-02 08:04:23 Re: Fix typo in CF App confirm dialog