Re: Unsigned integer types

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Maciej Gajewski <maciej(dot)gajewski0(at)gmail(dot)com>
Cc: 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-28 12:21:50
Message-ID: 51A4A15E.9060402@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 05/28/2013 05:17 AM, Maciej Gajewski wrote:
> I'm afraid that implementing uints as and extension would introduce
> some performance penalty (I may be wrong).

You are.

> I'm also afraid that with
> the extension I'd be left on my own maintaining it forever. While if
> this could go into the core product, it would live forever.

This is an argument against ever doing anything as an extension.

You have not at all addressed the real problem with doing what you are
asking for, the one that Tom Lane stated:

>> Basically, there is zero chance this will happen unless you can find
>> a way of fitting them into the numeric promotion hierarchy that doesn't
>> break a lot of existing applications. We have looked at this more than
>> once, if memory serves, and failed to come up with a workable design
>> that didn't seem to violate the POLA.
>>

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Szymon Guz 2013-05-28 12:22:13 Re: storing plpython global pointer
Previous Message Cédric Villemain 2013-05-28 12:16:38 Re: PostgreSQL 9.3 beta breaks some extensions "make install"