| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, 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 14:32:46 |
| Message-ID: | 4A7AE98E.8050804@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Kevin Grittner wrote:
> 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.
>
>
>
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-08-06 14:33:40 | Re: Adding error message "source" |
| Previous Message | Tom Lane | 2009-08-06 14:28:29 | Re: Re: [Pg-migrator-general] Composite types break pg_migrated tables |