| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
| Cc: | Alexander Korotkov <aekorotkov(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: GiST for range types (was Re: Range Types - typo + NULL string constructor) |
| Date: | 2011-11-02 19:29:31 |
| Message-ID: | 4EB19A1B.3070205@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 01.11.2011 06:33, Jeff Davis wrote:
> On Mon, 2011-10-24 at 15:05 +0400, Alexander Korotkov wrote:
>
>> I think implementing subtype_diff for each datatype is ok. We could
>> implement some universal function based on minus operator and casting
>> to double precision. But such solution might be unacceptable in
>> both predictability (operator and casting function might do not the
>> things we expect) and performance.
>>
> Done.
Thanks, I'm looking into this now.
> + else if (lower1.infinite || upper1.infinite)
> + length1 = 1.0/0.0;
That seems wrong. I take it that the point is to set length1 to infinity?
PS. I note the docs still refer to subtype_float. I'll fix that before
committing.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-11-02 19:48:22 | Re: GiST for range types (was Re: Range Types - typo + NULL string constructor) |
| Previous Message | Andrew Dunstan | 2011-11-02 19:27:28 | Re: superusers are members of all roles? |