Re: problem of geometric operator in v8.2.1

From: "Ioseph Kim" <pgsql-kr(at)postgresql(dot)or(dot)kr>
To: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: problem of geometric operator in v8.2.1
Date: 2007-02-02 21:21:21
Message-ID: 010301c74710$161767f0$1e00a8c0@IDC
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I misunderstood. :)

path '((0,0),(1,0))' is 'closed' path.

in this case, it's maybe operator calculated return length too.

----- Original Message -----
From: "Ioseph Kim" <pgsql-kr(at)postgresql(dot)or(dot)kr>
To: <pgsql-hackers(at)postgresql(dot)org>
Sent: Saturday, February 03, 2007 6:00 AM
Subject: Re: [HACKERS] problem of geometric operator in v8.2.1

> when @-@ operator used at path type,
> below query maybe returns 1.
> because this path is just line.
>
>
> ----- Original Message -----
> From: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
> To: "Ioseph Kim" <pgsql-kr(at)postgresql(dot)or(dot)kr>
> Cc: <pgsql-hackers(at)postgresql(dot)org>
> Sent: Saturday, February 03, 2007 5:36 AM
> Subject: Re: [HACKERS] problem of geometric operator in v8.2.1
>
>
>> "Ioseph Kim" <pgsql-kr(at)postgresql(dot)or(dot)kr> writes:
>>> => select @-@ lseg '((0,0),(1,0))';
>>> ?column?
>>> ----------
>>> 1
>>> (1 row)
>>
>>> => select @-@ path '((0,0),(1,0))';
>>> ?column?
>>> ----------
>>> 2
>>> (1 row)
>>
>>> It's maybe bug in v8.2.1
>>
>> What do you think is wrong with those answers?
>>
>> regards, tom lane
>>
>> ---------------------------(end of broadcast)---------------------------
>> TIP 2: Don't 'kill -9' the postmaster
>>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2007-02-02 21:36:52 Re: problem of geometric operator in v8.2.1
Previous Message Simon Riggs 2007-02-02 21:14:33 Re: Referential Integrity and SHARE locks