Re: BUG #4289: drop owned by report ERROR: cache lookup failed for relation 16390
От | Alvaro Herrera |
---|---|
Тема | Re: BUG #4289: drop owned by report ERROR: cache lookup failed for relation 16390 |
Дата | |
Msg-id | 20080709153241.GD3946@alvh.no-ip.org обсуждение исходный текст |
Ответ на | Re: BUG #4289: drop owned by report ERROR: cache lookup failed for relation 16390 (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: BUG #4289: drop owned by report ERROR: cache lookup failed for relation 16390
|
Список | pgsql-bugs |
Tom Lane wrote: > Alvaro Herrera <alvherre@commandprompt.com> writes: > > 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). > > Actually, on looking closer, the problem is that recursiveDeletion fails > to pass alreadyDeleted down to (and through) deleteDependentObjects. > So the cascaded delete doesn't get reported back to > performMultipleDeletions, and it doesn't know to skip the view when it > gets to it. So this is clearly a bug, and seemingly not so hard to fix. Hmm, in this case I wonder if this could show up in other cases too, like DROP SCHEMA. -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc.
В списке pgsql-bugs по дате отправления: