Re: Unsigned integer types

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Maciej Gajewski <maciej(dot)gajewski0(at)gmail(dot)com>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Bruce Momjian <bruce(at)momjian(dot)us>, Jim Nasby <jim(at)nasby(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Unsigned integer types
Date: 2013-05-29 17:48:17
Message-ID: alpine.DEB.2.02.1305291942590.25496@localhost6.localdomain6
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


I agree that extensions are undermarketed. Although pgxn is a good step,
I could not find it from "postgresql.org":-(

> I propose to not integrate the unsigned types into existing promotion
> hierarchy, and behave just like gcc would with -Werror: require
> explicit cast. Between them, the unsigned types would be automatically
> converted up (uint2 > uint4 > uint8).

If you do it, having uint1 (1 byte) would be nice as well.

--
Fabien.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Abhishek Rai 2013-05-29 18:45:21 Re: pg_stat_replication when standby is unreachable
Previous Message Heikki Linnakangas 2013-05-29 17:40:48 Re: XLogInsert scaling, revisited