Thread: BUG #12008: REASSIGN OWNED changes other databases

The following bug has been logged on the website:

Bug reference:      12008
Logged by:          Carlos Vásquez
Email address:      carlos.vasquez@clearcorp.co.cr
PostgreSQL version: 9.3.5
Operating system:   Ubuntu 14.04
Description:

Bug explained in stackoverflow
(http://stackoverflow.com/questions/27003415/postgres-reassign-owned-for-only-1-database).

I am using package 9.3.5-0ubuntu0.14.04.1 in ubuntu 14.04 without any
modification.

If I have multiple databases owned by user1 and I run REASSIGN OWNED BY
user1 TO user2; in 1 specific database, the command also changes the owner
of the other databases that user1 owns. This affects only the databases, not
the objects inside. Only the objects in the open database get changed to
user2 as it should be.

carlos.vasquez@clearcorp.co.cr wrote:

> Bug explained in stackoverflow
> (http://stackoverflow.com/questions/27003415/postgres-reassign-owned-for-only-1-database).
>
> I am using package 9.3.5-0ubuntu0.14.04.1 in ubuntu 14.04 without any
> modification.
>
> If I have multiple databases owned by user1 and I run REASSIGN OWNED BY
> user1 TO user2; in 1 specific database, the command also changes the owner
> of the other databases that user1 owns. This affects only the databases, not
> the objects inside. Only the objects in the open database get changed to
> user2 as it should be.

Yeah, the manual documents that this is what happens.  Is this a
problem?  Why?  I guess if there's a valid use case for not changing
global objects we could have a flag that only local objects are
affected.

--
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services