From: | Shubham Barai <shubhambaraiss(at)gmail(dot)com> |
---|---|
To: | Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> |
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: [HACKERS] GSoC 2017: weekly progress reports (week 6) |
Date: | 2018-01-02 15:31:08 |
Message-ID: | CALxAEPttGZqmg-1Sjvdcz_CT0mugqeTvgDaN1bvgxTZMZ8Qgew@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-www |
On 2 October 2017 at 22:21, Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>
wrote:
> 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.
>
>
I have created new isolation tests. Please have a look at
updated patch.
Regards,
Shubham
Attachment | Content-Type | Size |
---|---|---|
Predicate-locking-in-gin-index_4.patch | application/octet-stream | 44.8 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2018-01-02 15:35:16 | Re: [HACKERS] GnuTLS support |
Previous Message | Tom Lane | 2018-01-02 15:08:10 | Re: Better testing coverage and unified coding for plpgsql loops |
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2018-01-02 20:33:05 | Re: [pgcommitfest2] Sorting columns |
Previous Message | Craig Ringer | 2017-12-29 01:18:00 | Re: The pg_indent on on ftp is outdated |