| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, 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:36:58 |
| Message-ID: | 3615.1249569418@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)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 as its base type.
Arrays of domains would be a problem, if we had 'em, which we don't...
Also, as Peter already noted, arrays of built-in types are not really a
problem because the OID won't have changed since 8.3. It's only arrays
of types created post-initdb that are risk factors.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2009-08-06 14:40:43 | Re: Re: [Pg-migrator-general] Composite types break pg_migrated tables |
| Previous Message | Tom Lane | 2009-08-06 14:33:40 | Re: Adding error message "source" |