Re: 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: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: OID wraparound: summary and proposal
Date: 2001-08-02 00:58:14
Message-ID: 3B68A5A6.4AFB7C6F@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:
> > Tom Lane wrote:
> >>
> >> Given Hiroshi's objections, and the likelihood of compatibility problems
> >> for existing applications, I am now thinking that it's not a good idea to
> >> turn off OID generation by default.
>
> > Would OIDs be globally unique or per table ?
>
> Same as now: if you have a unique index on 'em, they're unique within a
> table; otherwise, no guarantee at all (once the system wraps around).
>

OIDs per table seems more important than others.

Strangely enough, I've seen no objection to optional OIDs
other than mine. Probably it was my mistake to have formulated
a plan on the flimsy assumption.

regards,
Hiroshi Inoue

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message mlw 2001-08-02 01:06:19 Re: OID wraparound: summary and proposal
Previous Message Mike Mascari 2001-08-02 00:49:26 Re: Is there a way to drop and restore an index?