Re: wrong message on REASSIGN OWNED - Mailing list pgsql-hackers

From Jaime Casanova
Subject Re: wrong message on REASSIGN OWNED
Date
Msg-id BANLkTinfRSVVTvDvPObxo+TcHJ6uM-FdXg@mail.gmail.com
Whole thread Raw
In response to Re: wrong message on REASSIGN OWNED  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
On Mon, Jun 13, 2011 at 10:37 AM, Alvaro Herrera
<alvherre@commandprompt.com> wrote:
> Excerpts from Robert Haas's message of sáb jun 11 21:01:55 -0400 2011:
>> On Thu, Jun 9, 2011 at 1:26 PM, Jaime Casanova <jaime@2ndquadrant.com> wrote:
>> > on shdepReassignOwned() we have this message, which is obviously wrong
>> > we are not dropping objects just reassigning them...
>> > """
>> >                       ereport(ERROR,
>> >
>> > (errcode(ERRCODE_DEPENDENT_OBJECTS_STILL_EXIST),
>> >                                   errmsg("cannot drop objects owned
>> > by %s because they are "
>> >                                                  "required by the
>> > database system",
>> >                                                  getObjectDescription(&obj))));
>> > """
>
> Oh my.  I introduced this mistake 6 years ago and nobody noticed in all
> this time.  I guess this is not a very frequently used feature.
>

well, i used it once last year... ;)
but the only reason i found this one was because i was giving a
training and it jumps out in the middle of it...

--
Jaime Casanova         www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación


pgsql-hackers by date:

Previous
From: Aidan Van Dyk
Date:
Subject: Re: FOREIGN TABLE doc fix
Next
From: Kohei KaiGai
Date:
Subject: Re: [v9.1] sepgsql - userspace access vector cache