| From: | Jean-Luc Lachance <jllachan(at)nsd(dot)ca> |
|---|---|
| To: | Joe Conway <mail(at)joeconway(dot)com> |
| Cc: | Rob Brown-Bayliss <rob(at)zoism(dot)org>, Andrew Sullivan <andrew(at)libertyrms(dot)info>, PostgreSQL General List <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: oid's and primary keys on insert |
| Date: | 2002-08-09 21:28:06 |
| Message-ID: | 3D5433E6.17416A6C@nsd.ca |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Joe Conway wrote:
> There is at least one good reason to not create oids on user tables:
> since they are generated from one source for the entire PostgreSQL
> cluster, in a large installation they can roll-over at 4 billion. By
> using them for system tables only, the concern of roll-over effectively
> goes away.
>
> There have been discussions of making per table oid generators but it
> doesn't look like that will happen for 7.3. I think going to 8 byte oids
> has been rejected to due to the performance hit and additional per row
> overhead.
>
We could have one sequence of OID (4 bytes) per table and a prefix (4
bytes) for a specific table in the system table. So we could have an
effective OID of 8 bytes and still keep the benefit of system wide
unique OID.
JLL
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nigel J. Andrews | 2002-08-09 22:01:30 | Re: oid's and primary keys on insert |
| Previous Message | Rob Brown-Bayliss | 2002-08-09 21:24:16 | Re: oid's and primary keys on insert |