From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Bug #6593, extensions, and proposed new patch policy |
Date: | 2012-04-18 16:05:03 |
Message-ID: | CA+TgmoYeLjDdLWmfNe=ntpAwmKzd+z28HifCm7Tj=RiT7UC6qQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Apr 18, 2012 at 11:41 AM, Alvaro Herrera
<alvherre(at)alvh(dot)no-ip(dot)org> wrote:
> Per bug #6593, REASSIGN OWNED fails when the affected role owns an
> extension. This would be trivial to fix if extensions had support code
> for ALTER EXTENSION / OWNER, but they don't. So the only back-patchable
> fix right now seems to be to throw an error on REASSIGN OWNED when the
> user owns an extension. (If anyone wants to claim that we ought to work
> on a real fix that allows changing the owner internally from REASSIGN
> OWNED, without introducing ALTER EXTENSION support for doing so, let me
> know and I'll see about it.)
I would be OK with the latter.
> In HEAD we can do the more invasive fix of actually adding support code
> for changing an extension's owner. And it seems to me that, going
> further, we should have a policy that any ownable object type we add
> must come with appropriate support for changing owner.
+1.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Emanuel Calvo | 2012-04-18 16:13:41 | [Devel 9.2] Index-only scan in count aggregation |
Previous Message | Alvaro Herrera | 2012-04-18 16:03:07 | Re: 8.4 path to repair_frag()? |