| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, 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_migrated tables |
| Date: | 2009-08-06 09:54:24 |
| Message-ID: | 200908061254.24485.peter_e@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thursday 06 August 2009 06:32:06 Bruce Momjian wrote:
> I have applied the attached patch to pg_migrator to detect enum,
> composites, and arrays. I tested it and the only error I got was with
> the breakmigrator table that was supplied by Jeff, and once I removed
> that table the migration went fine, meaning there are no cases of these
> stored in the regression test database.
That might be a bit excessive. As I understand it, arrays of built-in types
(e.g., int[]) should work fine. I suspect the majority of uses of arrays will
be with built-in types, so allowing that would help a significant portion of
installations.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2009-08-06 10:23:23 | Re: [COMMITTERS] pgsql: Use DocBook XSL stylesheets for man page building This switches |
| Previous Message | Pavel Stehule | 2009-08-06 09:41:55 | Re: the case for machine-readable error fields |