From: | Peter Eisentraut <e99re41(at)DoCS(dot)UU(dot)SE> |
---|---|
To: | Tom Cook <tcook(at)lisa(dot)com(dot)au> |
Cc: | "Pgsql-General(at)Postgresql(dot) Org" <pgsql-general(at)postgresql(dot)org> |
Subject: | RE: unique row identifier data type exhausted . . . |
Date: | 2000-04-26 13:53:34 |
Message-ID: | Pine.GSO.4.02A.10004261533170.15784-100000@Ekorre.DoCS.UU.SE |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, 26 Apr 2000, Tom Cook wrote:
> Is this necessarily a good solution? If you use 64-bit OIDs, some joker
> will just hook up a several-terra-byte disk array to his machine, try to
> store the location of every molecule in the universe and break it.
That's not going to work anyway. To store information about a molecule you
need at least one such molecule to hold that state, barring major
revolutions in storage technology. :-)
> Admittedly, ~2x10^20 is a very large number, but that's what they thought
> about 2000, also...
A while ago I said that in order to exhaust the oid space you need to add
1 million new records a day for more than 10 years. Then someone said, ok,
what if I have an email service with 1 million users that each get 10
emails a day. Then you're talking about 1 year. But in order to exhaust 64
bits, you can have 10^9 users (i.e., everyone), getting two million emails
a day for 1000 years. That seems pretty safe for as long as I care.
Of course to store all molecules you really need more like 384 bits.
> What I'm saying is, is there a better way of doing this?
Transfinite numbers ;)
--
Peter Eisentraut Sernanders väg 10:115
peter_e(at)gmx(dot)net 75262 Uppsala
http://yi.org/peter-e/ Sweden
From | Date | Subject | |
---|---|---|---|
Next Message | Justin Banks | 2000-04-26 14:28:17 | Re: plpgsql FOR <select> LOOP question |
Previous Message | Andras Balogh | 2000-04-26 11:49:39 | pgsql DATE |