Re: B-Tree support function number 3 (strxfrm() optimization) - Mailing list pgsql-hackers

From Claudio Freire
Subject Re: B-Tree support function number 3 (strxfrm() optimization)
Date
Msg-id CAGTBQpaQwEYgjs=Ob4n_MKSndyQ5fNX1+SNc6_SVCL1C+HQXgQ@mail.gmail.com
Whole thread Raw
In response to Re: B-Tree support function number 3 (strxfrm() optimization)  (Greg Stark <stark@mit.edu>)
List pgsql-hackers
On Fri, Apr 4, 2014 at 5:29 PM, Greg Stark <stark@mit.edu> wrote:
> Two questions I have:
>
> 1) Would it make more sense to use a floating point instead of an integer? I
> saw a need for a function like this when I was looking into doing GPU sorts.
> But GPUs expect floating point values.


In the context of this patch, I don't think you want to add
uncertainty to the != 0 or ==0 case (which is what FP would do).



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Using indices for UNION.
Next
From: Tom Lane
Date:
Subject: Re: Another thought about search_path semantics