From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: OID wraparound: summary and proposal |
Date: | 2001-08-01 19:21:19 |
Message-ID: | Pine.BSF.4.21.0108011211220.7195-100000@megazone23.bigpanda.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, 1 Aug 2001, Tom Lane wrote:
> Based on the discussion so far, here is an attempt to flesh out the
> details of what to do with OIDs for 7.2:
>
> 1. Add an optional clause "WITH OIDS" or "WITHOUT OIDS" to CREATE TABLE.
> The default behavior will be WITH OIDS.
>
> Note: there was some discussion of a GUC variable to control the default.
>
> Note: an alternative syntax possibility is to make it look like the "with"
> option clauses for functions and indexes: "WITH (oids)" or "WITH (noOids)".
> This is uglier today, but would start to look more attractive if we invent
> additional CREATE TABLE options in the future --- there'd be a place to
> put 'em. Comments?
I think a fixed default and placing it in parentheses are probably good
ideas.
> 3. For a table without OIDs, no entry will be made in pg_attribute for
> the OID column, so an attempt to reference the OID column will draw a
> "no such column" error. (An alternative is to allow OID to read as nulls,
> but it seemed that people preferred the error to be raised.)
Okay, at least the foreign key stuff will need to change (since it does a
select oid), but I don't think it ever does anything with that except
check for existance, so I could probably make it select 1 as reasonable
replacement.
From | Date | Subject | |
---|---|---|---|
Next Message | Stephan Szabo | 2001-08-01 19:22:07 | Re: Accessing different databases in a cluster |
Previous Message | Stephan Szabo | 2001-08-01 19:10:14 | Re: Problem with FK referential actions |