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

Re: GSoC

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 (view raw or flat)
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

In response to

  • Re: GSoC at 2010-03-30 13:54:58 from Robert Haas

Responses

  • Re: GSoC at 2010-03-31 00:07:33 from Robert Haas

pgsql-hackers by date

Next:From: Pavel StehuleDate: 2010-03-30 13:41:58
Subject: why table.name is translated to (name.*)::name?
Previous:From: Robert HaasDate: 2010-03-30 13:23:38
Subject: Re: Questions about 9.0 release note

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