Re: BUG #4289: drop owned by report ERROR: cache lookup failed for relation 16390

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: BUG #4289: drop owned by report ERROR: cache lookup failed for relation 16390
Дата
Msg-id 13285.1215616704@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: BUG #4289: drop owned by report ERROR: cache lookup failed for relation 16390  (Alvaro Herrera <alvherre@commandprompt.com>)
Ответы Re: BUG #4289: drop owned by report ERROR: cache lookup failed for relation 16390
Список pgsql-bugs
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.

            regards, tom lane

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: BUG #4289: drop owned by report ERROR: cache lookup failed for relation 16390
Следующее
От: Tom Lane
Дата:
Сообщение: Re: BUG #4289: drop owned by report ERROR: cache lookup failed for relation 16390