Received: from localhost (postgresql.org [64.49.215.8])
	by postgresql.org (Postfix) with ESMTP id 3279B475DC7
	for <pgsql-sql@postgresql.org>; Thu, 29 Aug 2002 09:34:10 -0400 (EDT)
Received: from wolff.to (wolff.to [66.92.219.49])
	by postgresql.org (Postfix) with SMTP id 1DC1D475C77
	for <pgsql-sql@postgresql.org>; Thu, 29 Aug 2002 09:34:09 -0400 (EDT)
Received: (qmail 9893 invoked by uid 500); 29 Aug 2002 13:41:29 -0000
Date: Thu, 29 Aug 2002 08:41:29 -0500
From: Bruno Wolff III <bruno@wolff.to>
To: Roger Mathis <traderx@gmx.ch>
Cc: pgsql-sql@postgresql.org
Subject: Re: signed/unsigned integers
Message-ID: <20020829134129.GA9800@wolff.to>
Mail-Followup-To: Roger Mathis <traderx@gmx.ch>,
	pgsql-sql@postgresql.org
References: <3d65fbf1$0$22439$5402220f@news.sunrise.ch>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3d65fbf1$0$22439$5402220f@news.sunrise.ch>
User-Agent: Mutt/1.3.25i
X-Virus-Scanned: by AMaViS new-20020517
X-Archive-Number: 200208/415
X-Sequence-Number: 9261

On Fri, Aug 23, 2002 at 11:11:51 +0200,
  Roger Mathis <traderx@gmx.ch> wrote:
> Hi
> 
> Is it true, that I can't define unsigned integers in a table definition?

If the main issue is that there not be negative numbers, you can use a
constraint to enforce this. In 7.3 you can define a domain with the
constraint and use it similar to a type.

If you need 32-63 bits worth of information, then you can use bigint with
some performance penalty. If you need 64 bits or more of information,
then you might be able to use numeric with an even larger performance hit.