| From: | Curt Sampson <cjs(at)cynic(dot)net> |
|---|---|
| To: | Jean-Luc Lachance <jllachan(at)nsd(dot)ca> |
| Cc: | PostgreSQL General List <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: oid's and primary keys on insert |
| Date: | 2002-08-12 03:28:34 |
| Message-ID: | Pine.NEB.4.44.0208121226130.2317-100000@angelic.cynic.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, 9 Aug 2002, Jean-Luc Lachance wrote:
> Joe Conway wrote:
>
> 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.
Or we could just create an explicit "object ID" column in those system
tables that need it, and drop the whole object IDs thing entirely. Then
all this confusion over the purpose of object IDs would go away.
cjs
--
Curt Sampson <cjs(at)cynic(dot)net> +81 90 7737 2974 http://www.netbsd.org
Don't you know, in this new Dark Age, we're all light. --XTC
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Randall Perry | 2002-08-12 04:26:21 | Craetalang function can't find libgcc_s.so.1 on Solaris 8 |
| Previous Message | Curt Sampson | 2002-08-12 03:25:06 | Re: oid's and primary keys on insert |