Re: BUG #2802: Feature request: tinyint and unsigned types

From: Jim Nasby <decibel(at)decibel(dot)org>
To: Bruno Wolff III <bruno(at)wolff(dot)to>
Cc: Albert Strasheim <fullung(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #2802: Feature request: tinyint and unsigned types
Date: 2006-12-09 02:25:02
Message-ID: 23FD7624-3255-4582-A3D4-1E7DB54AE737@decibel.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Dec 4, 2006, at 4:11 PM, Bruno Wolff III wrote:
> You can already use "char" to store 1 byte values, though unless
> there are
> several of these in a row, you won't save any space because of
> alignment.

<nitpick>There's also boolean...</nitpick>

Is there any technical reason why we don't support unsigned ints or
tinyint? Just a matter of no one feeling the itch?
--
Jim Nasby jim(at)nasby(dot)net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2006-12-09 06:37:48 Re: BUG #2802: Feature request: tinyint and unsigned types
Previous Message David Lee Lambert 2006-12-08 22:46:42 "Julian day" date format is off by 12 hours