aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistsplit.c
diff options
context:
space:
mode:
authorAlvaro Herrera <alvherre@alvh.no-ip.org>2012-07-03 15:09:59 -0400
committerAlvaro Herrera <alvherre@alvh.no-ip.org>2012-07-03 15:09:59 -0400
commit0c7b9dc7d037c4465227dc2300ff48019feeba37 (patch)
tree425cb7144ef4aa08de6bd979596b75fc7bb6717b /src/backend/access/gist/gistsplit.c
parentb33385b89d30ad3daa63b398e56a5e3822fd59c6 (diff)
downloadpostgresql-0c7b9dc7d037c4465227dc2300ff48019feeba37.tar.gz
postgresql-0c7b9dc7d037c4465227dc2300ff48019feeba37.zip
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.
Diffstat (limited to 'src/backend/access/gist/gistsplit.c')
0 files changed, 0 insertions, 0 deletions