| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, "spam_eater(at)gmx(dot)net" <spam_eater(at)gmx(dot)net>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>, Jaime Casanova <jaime(at)2ndquadrant(dot)com> |
| Subject: | Re: Re: BUG #7748: "drop owned by" fails with error message: "unrecognized object class: 1262" |
| Date: | 2013-01-28 20:04:59 |
| Message-ID: | 22507.1359403499@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> I had a look at what it'd take to backpatch. For REASSIGN OWNED, you're
> right that it'd require some refactoring, and it's probably not
> worthwhile (the code is not really all that complicated). However, for
> DROP OWNED the proposed hunks apply fine. Only 8.3 needs a different
> patch, but it's only because whitespace is different.
> So what we would end up with, is that DROP OWNED works for shared
> objects (i.e. grants on tablespaces and databases are revoked), but
> REASSIGN OWNED does not; so you're forced to do ALTER
> DATABASE/TABLESPACE SET OWNER.
> Since it's the grants that are more likely to cause headaches than
> ownership when trying to drop users, I suggest that applying those
> patches is the most convenient. (We know that this is a real problem
> because of the bug reports we've gotten.)
Seems reasonable to me.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Kirkwood | 2013-01-28 21:29:04 | Re: PL/R Median Busts Commit (Postgres 9.1.6 + plr 8.3.0.13 on Ubuntu 12.10 64 bit) |
| Previous Message | Alvaro Herrera | 2013-01-28 20:00:06 | Re: Re: BUG #7748: "drop owned by" fails with error message: "unrecognized object class: 1262" |