Re: GiST penalty functions [PoC]

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: amborodin(at)acm(dot)org
Cc: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Greg Stark <stark(at)mit(dot)edu>, Михаил Бахтерев <mob(at)k(dot)imm(dot)uran(dot)ru>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>, Михаил Бахтерев <mike(dot)bakhterev(at)gmail(dot)com>
Subject: Re: GiST penalty functions [PoC]
Date: 2016-10-03 03:45:46
Message-ID: CAB7nPqTAe7RRajEx=Mn0cUKj-jw5tTyqzQTbmWei8Dxb_4+yzg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Sep 22, 2016 at 3:45 AM, Andrew Borodin <borodin(at)octonica(dot)com> wrote:
> [blah]
>
> Practically, this algorithm cannot be implemented in current GiST API
> (only if we provide non-penalty-based choose subtree function,
> optional for GiST extension), but it certainly has scientific value.

This thread has basically died, so marking as returned with feedback.
If you feel that's not adapted, feel free to move it to next CF.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Craig Ringer 2016-10-03 03:48:51 Re: PATCH: Batch/pipelining support for libpq
Previous Message Michael Paquier 2016-10-03 03:38:19 Re: Cache Hash Index meta page.