From: | Neil Conway <nconway(at)klamath(dot)dyndns(dot)org> |
---|---|
To: | Curt Sampson <cjs(at)cynic(dot)net> |
Cc: | Jean-Luc Lachance <jllachan(at)nsd(dot)ca>, PostgreSQL General List <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: oid's and primary keys on insert |
Date: | 2002-08-12 15:23:45 |
Message-ID: | 87r8h4xfr2.fsf@klamath.dyndns.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Curt Sampson <cjs(at)cynic(dot)net> writes:
> 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.
IMHO, it would be a better idea to eventually change to not creating
OIDs by default on user tables (for backwards compatibility, we should
probably wait a little while to make this change -- but perhaps toggle
it with a GUC option, disabled by default, in the short-term?). Since
WITHOUT OIDS is a space optimization in development sources, we're
most of the way there already...
> 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.
As far as I can tell, OIDs on system tables are exactly that: an
explicit "object ID" column that uniquely identifies entries in system
catalogs.
Cheers,
Neil
--
Neil Conway <neilconway(at)rogers(dot)com>
PGP Key ID: DB3C29FC
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Sullivan | 2002-08-12 15:30:36 | Re: [HACKERS] Linux Largefile Support In Postgresql RPMS |
Previous Message | chris.gamble | 2002-08-12 15:22:32 | Max user connections from Postgres Linux 7.2.1 |