| From: | Reinhard Mueller <reinhard(dot)mueller(at)bytewise(dot)at> |
|---|---|
| To: | Neil Tiffin <ntiffin(at)earthlink(dot)net> |
| Cc: | Hannu Krosing <hannu(at)tm(dot)ee>, Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>, "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org, gnue-geas(at)lists(dot)gnue(dot)org |
| Subject: | Re: [gnue-geas] Re: Proposal: OID wraparound: summary and proposal |
| Date: | 2001-08-11 20:54:55 |
| Message-ID: | 3B759B9F.8040509@bytewise.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2001-08-11 20:59:49 | Re: [PATCHES] Select parser at runtime |
| Previous Message | Justin Clift | 2001-08-11 20:48:53 | Re: CREATE LANGUAGE |