Skip site navigation (1) Skip section navigation (2)

Re: [PgFoundry] Unsigned Data Types [1 of 2]

From: "Jaime Casanova" <jcasanov(at)systemguards(dot)com(dot)ec>
To: "Ryan Bradetich" <rbradetich(at)gmail(dot)com>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: [PgFoundry] Unsigned Data Types [1 of 2]
Date: 2008-09-08 06:34:30
Message-ID: 3073cc9b0809072334g49ac61b1h132592d730604b0@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-patches
On Mon, Sep 8, 2008 at 1:14 AM, Ryan Bradetich <rbradetich(at)gmail(dot)com> wrote:
>
>> If you read the comments around that stuff it leaves quite a lot to be
>> desired, but I don't really have better ideas at the moment.  The best
>> near-term solution for the uint module is probably not to rely on
>> scalarltsel/scalargtsel for uint comparisons, but to make its own
>> selectivity functions that know the uint types plus whatever standard
>> types you want to have comparisons with.
>
> Ok.  Looks like I need to review these functions and develop new functions
> specific for the unsigned type.
>

the same problem happens in joins, unions, hash, etc... so you have to
look at those functions as well

PS: Jaime not Jamie :)

-- 
regards,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. (593) 87171157

In response to

Responses

pgsql-patches by date

Next:From: Heikki LinnakangasDate: 2008-09-08 06:45:18
Subject: Re: [HACKERS] TODO item: Implement Boyer-Moore searching (First time hacker)
Previous:From: Ryan BradetichDate: 2008-09-08 06:14:43
Subject: Re: [PgFoundry] Unsigned Data Types [1 of 2]

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group