Re: BUG #7748: "drop owned by" fails with error message: "unrecognized object class: 1262" - Mailing list pgsql-bugs

From Jaime Casanova
Subject Re: BUG #7748: "drop owned by" fails with error message: "unrecognized object class: 1262"
Date
Msg-id CAJKUy5jD2K1YWOuzrc6YNv07zsAQJvpsVbqfX0auo8MFHD9tbQ@mail.gmail.com
Whole thread Raw
In response to Re: BUG #7748: "drop owned by" fails with error message: "unrecognized object class: 1262"  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: BUG #7748: "drop owned by" fails with error message: "unrecognized object class: 1262"
List pgsql-bugs
On Sun, Dec 9, 2012 at 11:13 PM, Alvaro Herrera
<alvherre@2ndquadrant.com> wrote:
> Tom Lane wrote:
>>
>> spam_eater@gmx.net writes:
>> > postgres=3D# create user testuser with password 'secret';
>> > CREATE ROLE
>> > postgres=3D# create database testdb owner testuser;
>> > CREATE DATABASE
>> > testdb=3D> drop owned by testuser;
>> > ERROR:  unrecognized object class: 1262
>>
>> I can reproduce this in all versions back to 8.3.  In 8.2, the role's
>> ownership of the database is silently ignored, which I think was the
>> design intention.  I doubt that we want DROP OWNED dropping whole
>> databases.  At most maybe we should raise a NOTICE?
>
> I broke it recently: fe3b5eb08
>

whatever is the right way to solve this... shouldn't we do something
similar in shdepReassignOwned() in which we are still ignoring shared
objects?

--
Jaime Casanova         www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitaci=F3n
Phone: +593 4 5107566         Cell: +593 987171157

pgsql-bugs by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: BUG #7748: "drop owned by" fails with error message: "unrecognized object class: 1262"
Next
From: Sandeep Thakkar
Date:
Subject: Re: BUG #7740: Installation cannot fine msi file