Message-ID: <3B6F7804.5A0CD46A@tm.ee>
Date: Tue, 07 Aug 2001 10:09:24 +0500
From: Hannu Krosing <hannu@tm.ee>
MIME-Version: 1.0
To: Neil Tiffin <ntiffin@earthlink.net>
CC: Zeugswetter Andreas SB <ZeugswetterA@wien.spardat.at>,
	"'Tom Lane'" <tgl@sss.pgh.pa.us>, pgsql-hackers@postgresql.org,
	gnue-geas@lists.gnue.org
Subject: Re: Proposal: OID wraparound: summary and proposal
References: 
 <11C1E6749A55D411A9670001FA6879633683C1@sdexcsrv1.f000.d0188.sd.spardat.at
	> <p05100301b79051af3171@[192.168.0.6]>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Neil Tiffin wrote:
> 
> I would just like to comment that for our project, GNU Enterprise, we
> use our own 128 bit object ID that is unique (UUID) for every row in
> all tables.
> 
> It seems to me, without having looked into it, that having both a
> PostgreSQL UID  and our own 128 bit objectid (UUID) is redundant and
> slows the whole process down.  But we are storing object data in the
> database and require and absolutely unique objectid.  We are planning
> for enterprise usage and expect to need 128 bits to uniquely define
> our objects.

Is it just an 128-bit int from a sequence or does it have some internal 
structure ?

What kind of enterprise do you expect to have more than 
18 446 744 073 709 551 615 of objects that can uniquely be identified 
by 64 bits ?

-------------
Hannu