Re: KNNGIST next step: adjusting indexAM API - Mailing list pgsql-hackers

From Dimitri Fontaine
Subject Re: KNNGIST next step: adjusting indexAM API
Date
Msg-id 87k4jt349q.fsf@hi-media-techno.com
Whole thread Raw
In response to Re: KNNGIST next step: adjusting indexAM API  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: KNNGIST next step: adjusting indexAM API  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane <tgl@sss.pgh.pa.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


pgsql-hackers by date:

Previous
From: Dimitri Fontaine
Date:
Subject: Re: pg_execute_from_file review
Next
From: "Kevin Grittner"
Date:
Subject: Re: profiling connection overhead