RE: unique row identifier data type exhausted . . .

From: Tom Cook <tcook(at)lisa(dot)com(dot)au>
To: "Pgsql-General(at)Postgresql(dot) Org" <pgsql-general(at)postgresql(dot)org>
Subject: RE: unique row identifier data type exhausted . . .
Date: 2000-04-25 23:49:21
Message-ID: Pine.LNX.4.10.10004260916090.29505-100000@frog.adl.ardec.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, 24 Apr 2000, Andrew Snow wrote:

> > When we are sure all platforms support 64-bit int's, we will move in
> > that direction.
>
> Sorry if this is a stupid question, but couldn't you fairly easily make it
> an option at compile time? To use either 32 or 64 bit OID's.
> (And, less importantly, for sequences)

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.

Admittedly, ~2x10^20 is a very large number, but that's what they thought
about 2000, also...

What I'm saying is, is there a better way of doing this?

Cheers
--
Tom Cook - Software Engineer

"Christ died for sin, the righteous for the unrighteous, to bring you to God."
- 1 Peter 3:18

LISAcorp - www.lisa.com.au

--------------------------------------------------
38 Greenhill Rd. Level 3, 228 Pitt Street
Wayville, SA, 5034 Sydney, NSW, 2000

Phone: +61 8 8272 1555 Phone: +61 2 9283 0877
Fax: +61 8 8271 1199 Fax: +61 2 9283 0866
--------------------------------------------------

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Franck Martin 2000-04-26 00:10:44 RE: unique row identifier data type exhausted . . .
Previous Message Martin A. Marques 2000-04-25 22:32:57 problem with databases