"Andrew Bartley" <abartley@evolvosystems.com> writes:
> We have found this to be a major problem. It seems once the OIDs wrap; we =
> constantly get errors due to "Cannot insert a duplicate key into unique ind=
> ex pg_class_oid_index". There are about 3,000 entries in pg_class at this =
> stage.
Once the OID counter wraps, there's certainly some risk of OID
collisions. However, if you have only 3000 entries in pg_class it's
hard to see why the odds would be worse than 3000/4billion or less than
one failure in 1 million tries. I think there is something you have not
told us.
The nearby suggestions to minimize the rate of OID consumption seem
rather beside the point from here ... what I'd wonder about is why you
need as many as three thousand tables. Reducing that footprint should
reduce the odds of OID collision.
regards, tom lane
