I wrote: > Andrew Dunstan <andrew.duns...@2ndquadrant.com> writes: >> OK, that seems to be the consensus. So let's apply the blacklist patch >> and then separately remove the 'created in the same transaction' test. >> We'll need to adjust the regression tests and docs accordingly.
> Agreed. I'll work on that in a little bit. Pushed; sorry for the delay. I noticed that the blacklist mechanism effectively removed the prohibition against using a renamed enum value later in the same transaction, so I added a regression test for that. Also, as committed, I used RENAME TYPE rather than ALTER OWNER in the test cases requiring an updated pg_type row. That way we don't need to create a role, even a transient one, which is a good thing in terms of not risking collisions with other sessions. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers