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

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "Bruce Momjian" <bruce(at)momjian(dot)us>
Cc: "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Jeff" <threshar(at)threshar(dot)is-a-geek(dot)com>
Subject: Re: Re: [Pg-migrator-general] Composite types break pg_migratedtables
Date: 2009-08-06 13:51:08
Message-ID: 4A7A997C020000250002953E@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan <andrew(at)dunslane(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-08-06 14:20:51 Re: Adding error message "source"
Previous Message Werner Echezuria 2009-08-06 13:36:03 Re: problem with splitting a string