From: | Zeugswetter Andreas SB <ZeugswetterA(at)Wien(dot)Spardat(dot)at> |
---|---|
To: | "'The Hermit Hacker'" <scrappy(at)hub(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | AW: Big 7.1 open items |
Date: | 2000-06-19 12:14:43 |
Message-ID: | 219F68D65015D011A8E000006F8590C605BA5977@sdexcsrv1.f000.d0188.sd.spardat.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp> writes:
> > > Please add my opinion for naming rule.
> >
> > > relname/unique_id but need some work new
> pg_class column,
> > > no relname change. for unique-id generation
> filename not relname
> >
> > Why is a unique ID better than --- or even different from ---
> > using the relation's OID? It seems pointless to me...
>
> just to open up a whole new bucket of worms here, but ... if
> we do use OID
> (which up until this thought I endorse 100%) ... do we not
> run a risk if
> we run out of OIDs? As far as I know, those are still a
> finite resource,
> no?
>
> or, do we just assume that by the time that comes, everyone
> will be pretty
> much using 64bit machines? :)
I think the idea is to have an option to remove oid's from
user tables. I don't think you will run out of oid's if you have your bulk
data
not use up oid's.
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2000-06-19 13:28:59 | Re: Big 7.1 open items |
Previous Message | Zeugswetter Andreas SB | 2000-06-19 12:09:31 | AW: Big 7.1 open items |