Florian Pflug <f...@phlo.org> writes:
> On Dec13, 2010, at 00:16 , Robert Haas wrote:
>> And in fact it strikes me that we might not have much choice about how
>> to fix this. I think we are not going to retroactively change the
>> behavior of ALTER DATABASE .. SET ROLE in a released version, but yet
>> we do, I think, want to make pg_upgrade work.
> A simple fix is to teach pg_upgrade to issue "RESET SESSION
AUTHORIZATION" immediately after connecting to a database.
How is that a fix? RESET is defined to reset to the state you get
immediately after connection. Including anything established by those
ALTER commands.
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
