Re: BUG #4289: drop owned by report ERROR: cache lookup failed for relation 16390 - Mailing list pgsql-bugs

From Alvaro Herrera
Subject Re: BUG #4289: drop owned by report ERROR: cache lookup failed for relation 16390
Date
Msg-id 20080709150842.GC3946@alvh.no-ip.org
Whole thread Raw
In response to Re: BUG #4289: drop owned by report ERROR: cache lookup failed for relation 16390  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: BUG #4289: drop owned by report ERROR: cache lookup failed for relation 16390  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Alvaro Herrera wrote:
> crystal wrote:
>
> > TEST=# drop owned by u1, u2 cascade;
> > NOTICE:  drop cascades to view v2
> > ERROR:  cache lookup failed for relation 16390
>
> Rats.  I guess this is due to the two-pass nature of some algorithm.
> (Dropping owned by u1 cascade drops the view too, and then when dropping
> owned by u2, it tries to find the view and the cache lookup fails).

This patch fixes it, but I'm not sure if it breaks some other case (not
awake enough yet I think).

The problem is that we're accumulating objects for all users in a single
pass, and then calling performMultipleDeletion with all of them.  As far
as I understand the comments in performMultipleDeletion, this should
work ...

--
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

Attachment

pgsql-bugs by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: BUG #4287: Will not boot
Next
From: Tom Lane
Date:
Subject: Re: BUG #4289: drop owned by report ERROR: cache lookup failed for relation 16390