From: | Dimitri Fontaine <dfontaine(at)hi-media(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Anindya Jyoti Roy <anindyar(at)iitk(dot)ac(dot)in>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: GSoC |
Date: | 2010-03-30 13:36:25 |
Message-ID: | 87sk7ivsme.fsf@hi-media-techno.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Tue, Mar 30, 2010 at 12:56 AM, Anindya Jyoti Roy <anindyar(at)iitk(dot)ac(dot)in> wrote:
>> As Jeff Davis pointed out, I followed the modification he suggested and now
>> I want to have a basic matching only. I think atleast the fingerprint
>> processing can be done in summer (if not the image processing). Is it a good
>> GSoC project now?
>
> I'm not sure. Can you provide a more detailed design?
Apply the following to fingerprint searches ?
http://www.postgresql.org/docs/current/static/gist-implementation.html
http://wiki.postgresql.org/wiki/Image:Prato_2008_prefix.pdf
I guess that what remains to be defined is how you get those
fingerprint, what the datatype is named, is it fixed size or varlena,
what operators you want to make available, and which will have index
support. That's GiST + GIN, right ?
Regards,
--
dim
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2010-03-30 13:41:58 | why table.name is translated to (name.*)::name? |
Previous Message | Robert Haas | 2010-03-30 13:23:38 | Re: Questions about 9.0 release note |