Re: Removing pg_migrator limitations

Andrew Dunstan <andrew@dunslane.net>

From: Andrew Dunstan <andrew@dunslane.net>
To: Bruce Momjian <bruce@momjian.us>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Greg Stark <gsstark@mit.edu>, PostgreSQL-development <pgsql-hackers@postgresql.org>, Alvaro Herrera <alvherre@alvh.no-ip.org>
Date: 2009-12-24T22:23:05Z
Lists: pgsql-hackers

Bruce Momjian wrote:
> As far as the ability to add enum values using ALTER TYPE, it seems we
> would need a pg_enum.enumnum column like we do for pg_attribute.attnum
> and order on that rather than pg_enum.oid.   (Binary upgrade would still
> need to preserve oids.)
>
>   

I don't that's necessarily a good way to go - being able to sort by the 
actual stored value is an efficiency point. I think we might need to 
look at implementing a more extensible enum type, which would allow new 
values to be appended to and possibly inserted into the list of labels, 
but anyway that's really a separate subject from pg_migrator.

cheers

andrew