Re: Re: [Pg-migrator-general] Composite types break pg_migrated tables

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: [Pg-migrator-general] Composite types break pg_migrated tables
Date: 2009-08-07 01:00:42
Message-ID: 200908070100.n7710g907749@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

David E. Wheeler wrote:
> 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?

Yes, I have regression tests I run but they are not in CVS, partly
because they are tied to other scripts I have to manage server settings.

Here are my scripts:

http://momjian.us/tmp/pg_migrator_test.tgz

One big problem is that pg_migrator fails as soon as it hits one of
these so there isn't much to automate.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2009-08-07 01:01:14 Re: Re: [Pg-migrator-general] Composite types break pg_migrated tables
Previous Message Bruce Momjian 2009-08-07 00:56:51 Re: Re: [Pg-migrator-general] Composite types break pg_migrated tables