Re: Designing an extension for feature-space similarity search

From: Jay Levitt <jay(dot)levitt(at)gmail(dot)com>
To: Alexander Korotkov <aekorotkov(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PG Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Designing an extension for feature-space similarity search
Date: 2012-02-17 19:32:18
Message-ID: 4F3EAB42.5080409@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alexander Korotkov wrote:
> On Fri, Feb 17, 2012 at 11:00 PM, Jay Levitt <jay(dot)levitt(at)gmail(dot)com
> <mailto:jay(dot)levitt(at)gmail(dot)com>> wrote:
>
At first I thought this posed a challenge for union; if I have these
points:
>
> (1,2)
> (2,1)
> (1,NULL)
>
> what's the union? I think the answer is to treat NULL box coordinates
> like LL = -infinity, UR = infinity, or (equivalently, I think) to store
> a saw_nulls bit in addition to LL and UR.
>
> Similar problem appears at GiST indexing of ranges, because range can be
> empty. There additional "contain empty" flag was introduced. This "contain
> empty" flag indicates that underlying value can be empty. So, this flag is
> set when union with empty range or other range with this flag set. It's
> likely you need similar flag for each dimension.

Ah, yes, exactly the same problem. So what led you to add a flag instead of
using the range NULL..NULL? I'm on the fence about choosing.

Jay

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Don Baccus 2012-02-17 19:39:17 Re: MySQL search query is not executing in Postgres DB
Previous Message Christopher Browne 2012-02-17 19:28:21 Re: MySQL search query is not executing in Postgres DB