| From: | Neil Conway <neilc(at)samurai(dot)com> |
|---|---|
| To: | Tino Wildenhain <tino(at)wildenhain(dot)de> |
| Cc: | Hrishikesh Deshmukh <hdeshmuk(at)gmail(dot)com>, Postgresql-General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: OIDS |
| Date: | 2005-06-21 00:18:37 |
| Message-ID: | 42B75CDD.2040507@samurai.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Tino Wildenhain wrote:
> Google or your favourite search engine helps :-)
>
> http://www.postgresql.org/files/documentation/books/aw_pgsql/node71.html
>
> is among the first results.
Unfortunately those docs are quite out of date. This page is better:
http://developer.postgresql.org/docs/postgres/datatype-oid.html
(This describes the behavior that will be the default in 8.1)
Specifically:
Object identifiers (OIDs) are used internally by PostgreSQL as primary
keys for various system tables.... The oid type is currently implemented
as an unsigned four-byte integer. Therefore, it is not large enough to
provide database-wide uniqueness in large databases, or even in large
individual tables. So, using a user-created table's OID column as a
primary key is discouraged. OIDs are best used only for references to
system tables.
-Neil
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jason Tesser | 2005-06-21 01:25:00 | problems with types after update to 8.0 |
| Previous Message | Teunis Peters | 2005-06-21 00:17:57 | users, address record restrictions |