"Aaron Harsh" <[EMAIL PROTECTED]> writes:
>> Tom Lane <[EMAIL PROTECTED]> 08/03/05 1:33 PM >>>
>> OID wraparound would explain that ...
> Fantastic. Will our plan ('set without oids', pg_dump, pg_restore) take care
> of the problem?
Only temporarily (ie, till the counter wraps around again). I
> Tom Lane <[EMAIL PROTECTED]> 08/03/05 1:33 PM >>>
> "Aaron Harsh" <[EMAIL PROTECTED]> writes:
> > We've just recently started seeing sporadic constraint violations on system
> > tables. For example:
> > duplicate key violates unique constraint "pg_class_oid_index" [for
> > Statement "CREATE
"Aaron Harsh" <[EMAIL PROTECTED]> writes:
> We've just recently started seeing sporadic constraint violations on system
> tables. For example:
> duplicate key violates unique constraint "pg_class_oid_index" [for
> Statement "CREATE TEMPORARY TABLE...
OID wraparound would explain that ...
> a
We've just recently started seeing sporadic constraint violations on system
tables. For example:
duplicate key violates unique constraint "pg_class_oid_index" [for Statement
"CREATE TEMPORARY TABLE...
and
duplicate key violates unique constraint "pg_toast_4292803267_index" [for
Statement