Re: AW: OID wraparound: summary and proposal

From: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: AW: OID wraparound: summary and proposal
Date: 2001-08-03 01:45:42
Message-ID: 3B6A0246.3EC9EE7F@tpf.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
>
> Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> writes:
> > Hmm there seems to be an assumption that people could
> > know whether they need OID or not for each table.
>
> A good point, and one reason not to make no-OIDs the default. I'm
> envisioning that people will turn off OIDs only for tables that they
> know will be very large and that they know they don't need OIDs for.
>

AFAIK few people have voted *OIDs by default* in the
first place. It seems to mean that *default* would
naturally(essentially) be changed to *WITH NO OIDS*.
The followings are the result of vote which I remember
well.

regards,
Hiroshi Inoue

"Mikheev, Vadim" wrote:
>
> > OK, we need to vote on whether Oid's are optional,
> > and whether we can have them not created by default.
>
> Optional OIDs: YES
> No OIDs by default: YES

Lamar Owen wrote:
>
> [trimmed cc:list]
> On Wednesday 18 July 2001 17:09, Bruce Momjian wrote:
> > OK, we need to vote on whether Oid's are optional, and whether we can
> > have them not created by default.
>
> [All the below IMHO]
>
> OID's should be optional.
>
> System tables that absolutely have to have OIDs may keep them.
>
> No new OID usage, period. Use some other unique primary key.
>
> Default user tables to no OIDs.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2001-08-03 01:47:42 Re: patch for contrib/intarray (current CVS)
Previous Message Christopher Kings-Lynne 2001-08-03 01:40:09 TRUNCATE question