Re: Covering GiST indexes

From: Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>
To: Andreas Karlsson <andreas(at)proxel(dot)se>
Cc: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Teodor Sigaev <teodor(at)sigaev(dot)ru>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Covering GiST indexes
Date: 2019-03-10 08:39:27
Message-ID: CAPpHfdskWRZW1pR7ZFGkTB_M7_=g8cXbDmBA+L73RQhVFZBWHQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Mar 8, 2019 at 11:58 AM Alexander Korotkov
<a(dot)korotkov(at)postgrespro(dot)ru> wrote:
> I made some adjustments for this patch:
> * Rename tupledesc and tructTupledesc to leafTupdesc and
> nonLeafTupdesc correspondingly. I think this makes things more clear.
> * Some improvements to docs and comments.
> * Revise commit message.
>
> I'm going to push this on no objections.

Pushed with some more small changes in docs.

------
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 David Rowley 2019-03-10 09:53:02 Re: Should we add GUCs to allow partition pruning to be disabled?
Previous Message David Rowley 2019-03-10 08:34:51 Re: Performance issue in foreign-key-aware join estimation