Re: Removing pg_migrator limitations

Bruce Momjian <bruce@momjian.us> writes:
> The remaining issue is pg_enum oids.  Because it will be difficult to
> pass an arbitrary number of oids into the backend, the idea was to
> assign each enum value separately.  If we implement this TODO item:

>     Allow adding/renaming/removing enumerated values to an existing
>     enumerated data type 

The reason that isn't implemented is that it's *hard* --- in fact,
it appears to be entirely impossible in the general case, unless you're
willing to change existing values of the enum on-disk.  I do not agree
that it's a good plan to try to solve that as a prerequisite to making
pg_migrator work.
        regards, tom lane