Re: [gnue-geas] Re: Proposal: OID wraparound: summary and proposal - Mailing list pgsql-hackers

From Reinhard Mueller
Subject Re: [gnue-geas] Re: Proposal: OID wraparound: summary and proposal
Date
Msg-id 3B759B9F.8040509@bytewise.at
Whole thread Raw
In response to Re: Proposal: OID wraparound: summary and proposal  (Neil Tiffin <ntiffin@earthlink.net>)
List pgsql-hackers
Neil Tiffin wrote:

> I have not even considered multiple database servers running different 
> database, which is our design goal.  In this case we would like to have 
> a slimmed down (and blazingly fast) PostgreSQL server in which we manage 
> the uid in our middleware.  This is because the uid must be unique 
> accross all servers and database vendors.  (I don't claim to be a 
> database guru, so if we are all wet here please feel free to help 
> correct our misunderstandings.)

I am not 100% sure, but I would believe that the 
oid/uid/whatever_we_call_it only has to be unique within the table.

At least as long as you don't exchange data between different databases. 
As soon as you transfer data from db a to db b, it's good to have an 
object id that is unique in the world.
-- 
Reinhard Mueller
GNU Enterprise project
http://www.gnue.org



pgsql-hackers by date:

Previous
From: "Joe Conway"
Date:
Subject: Re: int8 sequences --- small implementation problem
Next
From: "Serguei Mokhov"
Date:
Subject: Re: int8 sequences --- small implementation problem