Re: Re: [Pg-migrator-general] Composite types break pg_migrated tables - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Re: [Pg-migrator-general] Composite types break pg_migrated tables
Date
Msg-id 21845.1249527647@sss.pgh.pa.us
Whole thread Raw
In response to Re: Re: [Pg-migrator-general] Composite types break pg_migrated tables  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> Is there any danger that an oid used in, say, pg_enum in the old version 
> will be used in the catalog bootstrap in the new version?

No.  All initdb-assigned OIDs are less than 16K, and we never assign
such an OID post-initdb (not even when wrapping around).  We might get
into trouble if we ever run out of OIDs below 16K, but I don't foresee
that happening anytime soon.

Also, the design I sketched depends on the fact that it doesn't matter
if, say, a pg_proc row gets an OID that we also need to use in pg_enum.
We only need OID uniqueness within each specific catalog.  So we don't
need to control the OID assignments in catalogs other than the three
we are interested in.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Re: [Pg-migrator-general] Composite types break pg_migrated tables
Next
From: Bruce Momjian
Date:
Subject: Re: Re: [Pg-migrator-general] Composite types break pg_migrated tables