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

From David E. Wheeler
Subject Re: Re: [Pg-migrator-general] Composite types break pg_migrated tables
Date
Msg-id 45D6A414-355E-477B-BD20-F1479B9A73B5@kineticode.com
Whole thread Raw
In response to Re: Re: [Pg-migrator-general] Composite types break pg_migrated tables  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Re: [Pg-migrator-general] Composite types break pg_migrated tables  (Peter Eisentraut <peter_e@gmx.net>)
Re: Re: [Pg-migrator-general] Composite types break pg_migrated tables  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
On Aug 6, 2009, at 7:28 AM, Tom Lane wrote:

> That would cover the problem for OIDs needed during CREATE TABLE, but
> what about types and enum values?

I haven't been following this discussion very closely, but wanted to  
ask: is someone writing regression tests for these cases that  
pg_migrator keeps bumping into?

Best,

David


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Adding error message "source"
Next
From: Peter Eisentraut
Date:
Subject: Re: Re: [Pg-migrator-general] Composite types break pg_migrated tables