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

From Kevin Grittner
Subject Re: Re: [Pg-migrator-general] Composite types break pg_migratedtables
Date
Msg-id 4A7A997C020000250002953E@gw.wicourts.gov
Whole thread Raw
In response to Re: Re: [Pg-migrator-general] Composite types break pg_migrated tables  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: Re: [Pg-migrator-general] Composite types break pg_migratedtables  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
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.
-Kevin


pgsql-hackers by date:

Previous
From: Werner Echezuria
Date:
Subject: Re: problem with splitting a string
Next
From: Tom Lane
Date:
Subject: Re: Adding error message "source"