On Mar 25, 2016, at 11:50 AM, Andrew Dunstan <and...@dunslane.net> wrote:
> I don't believe anyone knows how to do that safely.
The core issue, for me, is that not being able to modify enum values in a
transaction breaks a very wide variety of database migration tools. Even a
very brutal solution like marking indexes containing the altered type invalid
on a ROLLBACK would be preferable to the current situation.
-- Christophe Pettus
Sent via pgsql-hackers mailing list (email@example.com)
To make changes to your subscription: