Re: BUG #7748: "drop owned by" fails with error message: "unrecognized object class: 1262"

From: Jaime Casanova <jaime(at)2ndquadrant(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, spam_eater(at)gmx(dot)net, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #7748: "drop owned by" fails with error message: "unrecognized object class: 1262"
Date: 2012-12-10 04:28:58
Message-ID: CAJKUy5jD2K1YWOuzrc6YNv07zsAQJvpsVbqfX0auo8MFHD9tbQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Sun, Dec 9, 2012 at 11:13 PM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)com> wrote:
> Tom Lane wrote:
>>
>> spam_eater(at)gmx(dot)net writes:
>> > postgres=# create user testuser with password 'secret';
>> > CREATE ROLE
>> > postgres=# create database testdb owner testuser;
>> > CREATE DATABASE
>> > testdb=> 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ón
Phone: +593 4 5107566 Cell: +593 987171157

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Sandeep Thakkar 2012-12-10 06:01:23 Re: BUG #7740: Installation cannot fine msi file
Previous Message Alvaro Herrera 2012-12-10 04:13:07 Re: BUG #7748: "drop owned by" fails with error message: "unrecognized object class: 1262"