pgsql: Have REASSIGN OWNED work on extensions, too - Mailing list pgsql-committers

From Alvaro Herrera
Subject pgsql: Have REASSIGN OWNED work on extensions, too
Date
Msg-id E1Sm8f4-0006GE-NA@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Have REASSIGN OWNED work on extensions, too

Per bug #6593, REASSIGN OWNED fails when the affected role has created
an extension.  Even though the user related to the extension is not
nominally the owner, its OID appears on pg_shdepend and thus causes
problems when the user is to be dropped.

This commit adds code to change the "ownership" of the extension itself,
not of the contained objects.  This is fine because it's currently only
called from REASSIGN OWNED, which would also modify the ownership of the
contained objects.  However, this is not sufficient for a working ALTER
OWNER implementation extension.

Back-patch to 9.1, where extensions were introduced.

Bug #6593 reported by Emiliano Leporati.

Branch
------
REL9_1_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/ac50404224e5abb74b00bf22139f6ab96b01b2ab

Modified Files
--------------
src/backend/catalog/pg_shdepend.c |    5 ++
src/backend/commands/extension.c  |   92 +++++++++++++++++++++++++++++++++++++
src/include/commands/extension.h  |    2 +
3 files changed, 99 insertions(+), 0 deletions(-)


pgsql-committers by date:

Previous
From: Bruce Momjian
Date:
Subject: pgsql: Have copyright tool mention that certain files should be updated
Next
From: Alvaro Herrera
Date:
Subject: pgsql: Have REASSIGN OWNED work on extensions, too