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

From Andrew Dunstan
Subject Re: Re: [Pg-migrator-general] Composite types break pg_migratedtables
Date
Msg-id 4A7AE98E.8050804@dunslane.net
Whole thread Raw
In response to Re: Re: [Pg-migrator-general] Composite types break pg_migratedtables  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Responses Re: Re: [Pg-migrator-general] Composite types break pg_migratedtables  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers

Kevin Grittner wrote:
> Andrew Dunstan <andrew@dunslane.net> wrote:
>  
>   
>> Excluding every database that has a composite/array-of 
>> user-defined-type/enum type would be pretty nasty. After all, these
>> are features we boast of.
>>     
>  
> Any idea whether domains are an issue?  I was thinking of trying this
> tool soon, and we don't seem to be using any of the problem features
> -- unless type issues include domains.
>  
>
>   

I don't believe that they are an issue. The issue arises only when a 
catalog oid is used in the on-disk representation of a type. AFAIK the 
on-disk representation of a domain is the same as its base type.

cheers

andrew


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Re: [Pg-migrator-general] Composite types break pg_migrated tables
Next
From: Tom Lane
Date:
Subject: Re: Adding error message "source"