Re: Documentation: GiST extension implementation

From: Dimitri Fontaine <dfontaine(at)hi-media(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org>, Teodor Sigaev <teodor(at)sigaev(dot)ru>
Subject: Re: Documentation: GiST extension implementation
Date: 2009-06-13 07:11:54
Message-ID: C2D2814A-B9DF-4E38-9453-4D17A6560AFB@hi-media.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Le 12 juin 09 à 23:20, Tom Lane a écrit :
> Dimitri Fontaine <dfontaine(at)hi-media(dot)com> writes:
>> Le 12 juin 09 à 21:49, Tom Lane a écrit :
>>> It seems to me it could still do
>>> with a lot more detail to specify what API the functions are really
>>> expected to implement.
>
> What's bothering me is the fuzziness of the API
> specifications for the support functions. It's not real clear for
> example what you have to do to have an index storage type different
> from
> the column datatype, and even less clear which type the same()
> function
> is comparing. Having some skeletons that execute magic bits of
> undocumented code is not a substitute for a specification.

Oh yes that wasn't easy to guess: I had to look at others
implementations then do some tests (trial&error) to determine this.
Andrew Gierth has been really helpful here, and his ip4r module a good
example (but without varlena).
I'll try to provide something here, what I'm trying to say is that I
need some help and research (and core code reading) to reverse
engineer the specs.

Regards,
--
dim

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David Fetter 2009-06-13 08:33:59 Re: [GENERAL] Using results from DELETE ... RETURNING
Previous Message Fujii Masao 2009-06-13 03:02:45 Re: cannot update to the latest CVS sources