From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | carlos(dot)vasquez(at)clearcorp(dot)co(dot)cr |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #12008: REASSIGN OWNED changes other databases |
Date: | 2014-11-20 14:06:10 |
Message-ID: | 20141120140610.GI1639@alvin.alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
carlos(dot)vasquez(at)clearcorp(dot)co(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | LesLee Cox | 2014-11-20 14:19:59 | |
Previous Message | al.shuranov | 2014-11-20 12:31:03 | BUG #12012: After the upgrade PostgreSQL 9.2.4 -> 9.2.9 Missing "actual time" in auto_explain plans |