From: | Jaime Casanova <jaime(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: wrong message on REASSIGN OWNED |
Date: | 2011-06-13 14:49:44 |
Message-ID: | BANLkTinDVsk=TGxUzYL7qcs0_HRnmQ6i+Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Jun 13, 2011 at 8:55 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> On Mon, Jun 13, 2011 at 2:41 AM, Jaime Casanova <jaime(at)2ndquadrant(dot)com> wrote:
>>> btw, i'm allowed to use ALTER TABLE to assign a new owner (even an
>>> unprivileged one) to a system catalog, probably that's a bug.
>
>> +1 for tightening that up in 9.2.
>
> Nonsense. You won't like the results of "DELETE FROM pg_proc;" either,
> but we don't try to put training wheels on superusers.
>
really? i thought we do when system catalogs are involved based on this example:
"""
db=# alter table pg_largeobject set tablespace tblspc_prueba;
ERROR: permission denied: "pg_largeobject" is a system catalog
"""
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2011-06-13 15:01:32 | Re: FOREIGN TABLE doc fix |
Previous Message | Tom Lane | 2011-06-13 14:36:56 | Re: FOREIGN TABLE doc fix |