Re: BUG #13666: REASSIGN OWNED BY doesn't affect the relation underlying composite type

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: cpacejo(at)clearskydata(dot)com
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #13666: REASSIGN OWNED BY doesn't affect the relation underlying composite type
Date: 2015-12-11 21:54:45
Message-ID: 20151211215445.GW2763@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Alvaro Herrera wrote:
> cpacejo(at)clearskydata(dot)com wrote:

> > Furthermore, while trying to replicate in another database, I encountered:
> >
> > =# REASSIGN OWNED BY user1 TO user2;
> > ERROR: unexpected classid 1418
> >
> > Not sure if this is related or not.
>
> Not related. 1418 is pg_user_mapping (FDW stuff). Not sure what should
> happen here; my inclination without thinking too hard is that REASSIGN
> OWNED should ignore that object and DROP OWNED should remove it.

Ouch, I just noticed that you had already reported this months ago, and
I was even aware of it! I just pushed a fix for it without mentioning
you as first reporter :-(

I'm now looking at the other problem you reported here.

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message michael@sqlexec.com 2015-12-11 21:56:50 Re: BUG #13804: pg_restore returns unexpected error
Previous Message michael@sqlexec.com 2015-12-11 21:52:56 Re: BUG #13804: pg_restore returns unexpected error