Re: pgsql: Allow opclasses to provide tri-valued GIN consistent functions.

From: Thom Brown <thom(at)linux(dot)com>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)iki(dot)fi>
Cc: pgsql-committers <pgsql-committers(at)postgresql(dot)org>
Subject: Re: pgsql: Allow opclasses to provide tri-valued GIN consistent functions.
Date: 2014-03-13 12:55:13
Message-ID: CAA-aLv4nOYV1u1uAjMYktDShszvHdc+UV35MFfKKKtAniL6OLQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On 12 March 2014 15:52, Heikki Linnakangas <heikki(dot)linnakangas(at)iki(dot)fi> wrote:
> Allow opclasses to provide tri-valued GIN consistent functions.
>
> With the GIN "fast scan" feature, GIN can skip items without fetching all
> the keys for them, if it can prove that they don't match regardless of
> those keys. So far, it has done the proving by calling the boolean
> consistent function with all combinations of TRUE/FALSE for the unfetched
> keys, but since that's O(n^2), it becomes unfeasible with more than a few
> keys. We can avoid calling consistent with all the combinations, if we can
> tell the operator class implementation directly which keys are unknown.
>
> This commit includes a triConsistent function for the built-in array and
> tsvector opclasses.
>
> Alexander Korotkov, with some changes by me.

Patch to fix a couple typos attached.

--
Thom

Attachment Content-Type Size
patch_me_maybe.patch text/x-patch 1.2 KB

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Heikki Linnakangas 2014-03-13 13:02:40 pgsql: Fix a couple of typos in docs.
Previous Message Bruce Momjian 2014-03-13 05:42:33 pgsql: C comments: remove odd blank lines after #ifdef WIN32 lines