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

From Alvaro Herrera
Subject Re: Re: [Pg-migrator-general] Composite types break pg_migrated tables
Date
Msg-id 20090806000156.GA3638@alvh.no-ip.org
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  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > I received the following pg_migrator bug report today and was able to
> > reproduce the reported failure when using composite types:
> 
> >     test=> SELECT * FROM breakmigrator;
> >     ERROR:  cache lookup failed for type 27604
> 
> Hm ... has anyone tested pg_migrator using either composite types or
> arrays of user-defined types?  Both of them have got user-defined-type
> OIDs in on-disk data, now that I think about it.  For that matter, enums
> are going to be a problem too.

Don't arrays have embedded element OIDs too?

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: slow commits with heavy temp table usage in 8.4.0
Next
From: Tom Lane
Date:
Subject: Re: Re: [Pg-migrator-general] Composite types break pg_migrated tables