Skip site navigation (1) Skip section navigation (2)

Re: KNNGIST next step: adjusting indexAM API

From: Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, 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 15:24:17
Message-ID: 87k4jt349q.fsf@hi-media-techno.com (view raw or flat)
Thread:
Lists: pgsql-hackers
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> Right, AFAIK there is nothing in KNNGIST that would involve an on-disk
> data change.

Nice, that matches my Royal Oak memories.

But any external module relying on GiST will have to provide for the new
function you're thinking about, right? Updating was already needed to
cope with the newer consistent API, I guess. Will stop commenting now
until I've had the time to read the codeĀ :)

Regards,
-- 
Dimitri Fontaine
http://2ndQuadrant.fr     PostgreSQL : Expertise, Formation et Support

In response to

Responses

pgsql-hackers by date

Next:From: Kevin GrittnerDate: 2010-12-01 15:26:24
Subject: Re: profiling connection overhead
Previous:From: Dimitri FontaineDate: 2010-12-01 15:21:50
Subject: Re: pg_execute_from_file review

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group