Re: Re: OID wraparound: summary and proposal

mlw wrote:
> 
> Hiroshi Inoue wrote:
> >
> > The analog of ROWID in PostgreSQL is TID rather than OID
> > because TID is a physical address of a tuple within a table.
> > However there's a significant difference. Unfortunately TID
> > is transient. It is changed by UPDATE and  VACUUM.
> > Though TIDs are unavailable for critical use, OIDs could
> > compensate the drawback. TIDs and OIDs must help each
> > other if PostgreSQL needs the concept like ROWID.
> 
> That is true now, but I am saying that it should not be true. Rather than have
> a single limited global resource, the current OID, if possible, tables should
> get their own notion of an OID, like a ROWID.
> 

I've objected optional OID but never objected OIDs per table.
OIDs per table is more important than others IMHO.

regards,
Hiroshi Inoue