Re: OID wraparound (was Re: pg_depend)

From: Horst Herb <horst(at)hherb(dot)com>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: OID wraparound (was Re: pg_depend)
Date: 2001-07-19 03:03:28
Message-ID: 01071913032800.02053@munin.gnumed.dhs.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thursday 19 July 2001 06:08, you wrote:
> > Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:

> I think it should be off on user tables by default, but kept on system
> tables just for completeness. It could be added at table creation time
> or from ALTER TABLEL ADD. It seems we just use them too much for system
> stuff. pg_description is just one example.

and what difference should it make, to have a few extra hundred or thousand
OIDs used by system tables, when I insert daily some ten thousand records
each using an OID for itself?

Why not make OIDs 64 bit? Might slow down a little on legacy hardware, but in
a couple of years we'll all run 64 bit hardware anyway.

I believe that just using 64 bit would require the least changes to Postgres.
Now, why would that look that obvious to me and yet I saw no mentioing of
this in the recent postings. Surely it has been discussed before, so which is
the point I miss or don't understand?

I would need 64 bit sequences anyway, as it is predictable that our table for
pathology results will run out of unique IDs in a couple of years.

Horst

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Lincoln Yeoh 2001-07-19 03:23:06 Re: OID wraparound (was Re: pg_depend)
Previous Message Tom Lane 2001-07-19 02:42:00 RPM source files should be in CVS (was Re: psql -l)