Re: B-Tree support function number 3 (strxfrm() optimization)

From: Claudio Freire <klaussfreire(at)gmail(dot)com>
To: Greg Stark <stark(at)mit(dot)edu>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Geoghegan <pg(at)heroku(dot)com>, Thom Brown <thom(at)linux(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: B-Tree support function number 3 (strxfrm() optimization)
Date: 2014-04-04 21:23:49
Message-ID: CAGTBQpaQwEYgjs=Ob4n_MKSndyQ5fNX1+SNc6_SVCL1C+HQXgQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Apr 4, 2014 at 5:29 PM, Greg Stark <stark(at)mit(dot)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).

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2014-04-04 21:24:00 Re: Another thought about search_path semantics
Previous Message Tom Lane 2014-04-04 20:57:54 Re: Using indices for UNION.