Re: [PATCH] Covering SPGiST index

From: Pavel Borisov <pashkin(dot)elfe(at)gmail(dot)com>
To: "Andrey M(dot) Borodin" <x4mmm(at)yandex-team(dot)ru>
Cc: Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [PATCH] Covering SPGiST index
Date: 2020-08-31 11:57:56
Message-ID: CALT9ZEGWbX0c=DqjoLhD_LraA0fqSuwyEySr1HQtzwp9Tug8VQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>
> But let's change macro a bit. When I see
> SGLT_SET_OFFSET(leafTuple->nextOffset, InvalidOffsetNumber);
> I expect that leafTuple->nextOffset is function argument by value and will
> not be changed.
> For example see ItemPointerSetOffsetNumber() - it's not exposing ip_posid.
>
> Also, I'd propose instead of
> >*(leafChainDatums + i * natts) and leafChainIsnulls + i * natts
> using something like
> >int some_index = i * natts;
> >leafChainDatumsp[some_index] and &leafChainIsnulls[some_index]
> But, probably, it's a matter of taste...
>
> Also I'm not sure would it be helpful to use instead of
> >isnull[0] and leafDatum[0]
> more complex
> >#define SpgKeyIndex 0
> >isnull[SpgKeyIndex] and leafDatum[SpgKeyIndex]
> There is so many [0] in the patch...
>
I agree with all of your proposals and integrated them into v9.
Thank you very much!

--
Best regards,
Pavel Borisov

Postgres Professional: http://postgrespro.com <http://www.postgrespro.com>

Attachment Content-Type Size
v9-0001-Covering-SP-GiST-index-support-for-INCLUDE-column.patch application/octet-stream 78.1 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Borisov 2020-08-31 12:02:22 Re: Yet another fast GiST build (typo)
Previous Message Amit Kapila 2020-08-31 11:29:06 Use T_IntList for uint32