Message-ID: <56701006.4050004@elegosoft.com>
Date: Tue, 15 Dec 2015 14:05:10 +0100
From: Michael Anderson <michael.anderson@elegosoft.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: pgsql-admin@postgresql.org
Subject: [REASSIGN confusion]
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

I'm confused about the usage (or purpose) of REASSIGN.
If I've understood the docs correctly, REASSIGN changes the ownership of 
all database owned by old_role to new_role, as well as all objects on 
the *currently* connected database.

It seems to me that the most common task for an administrator would be 
to either:

change ownership of all objects on a single database owned by old_role 
without affecting any other databases
or
change ownership of all objects on all databases owned by old_role.

As I understand it, I can't use REASSIGN to perform either of these 
tasks. Or am I missing something?

Thanks,

Mike

-- 
--
Michael Anderson
IT Services & Support

elego Software Solutions GmbH
Gustav-Meyer-Allee 25
Building 12.3 (BIG) room 227
13355 Berlin, Germany

phone +49 30 23 45 86 96      michael.anderson at elegosoft.com
fax   +49 30 23 45 86 95      http://www.elegosoft.com

Geschaeftsfuehrer: Olaf Wagner, Sitz Berlin Amtsgericht
Berlin-Charlottenburg, HRB 77719, USt-IdNr: DE163214194


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin