Re: [HACKERS] On improving OO support in posgresql and relaxing oid bottleneck at the same time

> -----Original Message-----
> From: Maurice Gittens <mgittens(at)gits(dot)nl>
> To: hackers(at)postgreSQL(dot)org <hackers(at)postgreSQL(dot)org>
> Date: zondag 5 april 1998 21:47
> Subject: [HACKERS] On improving OO support in posgresql and relaxing oid
> bottleneck at the same time
>
> top most base class. In which all tuples are stored. Otherwise
> we'll storagefile independant oid's will become necesary again.
>
> So loosely speaking it still allows for multiple inheritance but only within
> a common hierarchy.

Just for everyones information. In Illustra, an oid is 64 bits. The low
order 32 bits are (approximately), the row identifier within a table. The
high order 32bits the table identifier (which then works out to be the
same as the oid of the row in the tables table for the table in question).

Oids are unique for the life of the system. Limits are 4G tables, 4G rows
per table.

I for some reason have never bothered to remember, but I think inheritance
is done via separate tables.

-dg

David Gould dg(at)illustra(dot)com 510.628.3783 or 510.305.9468
Informix Software (No, really) 300 Lakeside Drive Oakland, CA 94612
- Linux. Not because it is free. Because it is better.