From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, Teodor Sigaev <teodor(at)sigaev(dot)ru>, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: KNNGIST next step: adjusting indexAM API |
Date: | 2010-12-01 14:51:20 |
Message-ID: | 15487.1291215080@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Wed, Dec 1, 2010 at 5:22 AM, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr> wrote:
>> IIRC, the goal here was to be able to benefit from KNN GiST from
>> existing GiST indexes as soon as you restart the server with the new
>> code compiled in. I'm not sure it's that important in the context of
>> preparing 9.1. It seems that pg_upgrade already has to issue a reindex
>> script for GiST indexes.
> I don't think Tom was proposing to change the on-disk format, just the API.
Right, AFAIK there is nothing in KNNGIST that would involve an on-disk
data change.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Mario Weilguni | 2010-12-01 14:51:35 | Re: DELETE with LIMIT (or my first hack) |
Previous Message | Yeb Havinga | 2010-12-01 14:51:12 | Re: FK's to refer to rows in inheritance child |