Re: Improving deadlock error messages

Поиск
Список
Период
Сортировка
От Gregory Stark
Тема Re: Improving deadlock error messages
Дата
Msg-id 87irbra0fk.fsf@oxford.xeocode.com
обсуждение исходный текст
Ответ на Re: Improving deadlock error messages  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
"Tom Lane" <tgl@sss.pgh.pa.us> writes:

> 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.

We could do the syscache lookups for only the object we're waiting on and
store that information in the lock table for others to refer to. We would have
to do the syscache lookup either always or at the point where we first decide
we have to block.


--  Gregory Stark EnterpriseDB          http://www.enterprisedb.com



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

Предыдущее
От: Marcin Waldowski
Дата:
Сообщение: Re: [BUGS] BUG #3242: FATAL: could not unlock semaphore: error code 298
Следующее
От: Koichi Suzuki
Дата:
Сообщение: Re: [PATCHES] Full page writes improvement, code update