Re: Improving deadlock error messages

Поиск
Список
Период
Сортировка
От Neil Conway
Тема Re: Improving deadlock error messages
Дата
Msg-id 1177091158.16415.90.camel@localhost.localdomain
обсуждение исходный текст
Ответ на Re: Improving deadlock error messages  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Improving deadlock error messages  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
On Fri, 2007-04-20 at 02:55 -0400, Tom Lane wrote:
> I don't think you've thought of quite all of the failure cases.  One
> that's a bit pressing is that a deadlock isn't necessarily confined to
> objects in your own database.

I'm not sure I follow. If we conditionally acquire the locks we need and
always fallback to just printing the numeric OIDs, ISTM we should be
able to avoid the infinite recursion problem. (If necessary, we can
always special-case objects outside our own database, although I'm not
sure that's necessary.)

-Neil




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

Предыдущее
От: Andrew Dunstan
Дата:
Сообщение: Re: Re: [BUGS] BUG #3242: FATAL: could not unlock semaphore: error code 298
Следующее
От: Gregory Stark
Дата:
Сообщение: 27 second plan times