> At the SQL level, these datatypes are named after byte sizes not bit
> sizes, ie, int2, int4, int8. Or you might prefer smallint, int, bigint.
> There are no unsigned types.
>
> regards, tom lane
>
oh!! that makes it clear :)
thanks!
regards,
KM
--
km <[EMAIL PROTECTED]> writes:
> i have compiled postgres 8.1.4 even if configure didnt detect
> int8,uint8,int64 and uint64. i have tried to create a test table with
> datattype as int64 , but it says no such datatype, same is with uint8
> an uint64 datatypes.
At the SQL level, these datatypes a
> > I'd say, this is expected output from configure. Configure is just a
> > mechanism
> > to help constructing an abstraction for different types of OS (i.e. things
> > like "can we use this C type? Do we need to use another type instead?").
> > | how can i add int8,uint8,int64 and uint64 functi
On Fri, Sep 29, 2006 at 11:48:09AM +0200, Thomas Pundt wrote:
> I'd say, this is expected output from configure. Configure is just a mechanism
> to help constructing an abstraction for different types of OS (i.e. things
> like "can we use this C type? Do we need to use another type instead?").
>
Hi,
On Friday 29 September 2006 11:01, km wrote:
| i am compiling postgresql 8.1.4 on AMB x86_64 platform.
| configure runs fine but shows output (snippet shown) as follows:
| ...
| checking for int8... no
| checking for uint8... no
| checking for int64... no
| checking for uint64... no
I'd say
Hi all,
i am compiling postgresql 8.1.4 on AMB x86_64 platform.
configure runs fine but shows output (snippet shown) as follows:
...
checking for int8... no
checking for uint8... no
checking for int64... no
checking for uint64... no
...
my gcc -v gives me:
Reading specs from /usr/lib/gcc/x86
