Re: [HACKERS] Re: [Pg-migrator-general] Composite types break pg_migratedtables

2009-08-06 Thread Kevin Grittner
Andrew Dunstan and...@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

Re: [HACKERS] Re: [Pg-migrator-general] Composite types break pg_migratedtables

2009-08-06 Thread Andrew Dunstan
Kevin Grittner wrote: Andrew Dunstan and...@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

Re: [HACKERS] Re: [Pg-migrator-general] Composite types break pg_migratedtables

2009-08-06 Thread Tom Lane
Andrew Dunstan and...@dunslane.net writes: Kevin Grittner wrote: Any idea whether domains are an issue? 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