Re: Reducing likelihood of deadlocks (was referential Integrity and SHARE locks)

Поиск
Список
Период
Сортировка
От Marc Munro
Тема Re: Reducing likelihood of deadlocks (was referential Integrity and SHARE locks)
Дата
Msg-id 1171384847.6326.34.camel@bloodnok.com
обсуждение исходный текст
Ответ на Re: Reducing likelihood of deadlocks (was referential Integrity and SHARE locks)  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
Дерево обсуждения 
On Tue, 2007-13-02 at 11:38 -0500, Tom Lane wrote:
> Marc Munro <marc@bloodnok.com> writes:
> > From an application developer's standpoint there are few options, none
> > of them ideal:
>
> How about
>
> 4) Make all the FK constraints deferred, so that they are only checked
> at end of transaction.  Then the locking order of transactions that only
> modify C is always C1, C2, ..., P.

Excellent suggestion.  Thank you.

__
Marc

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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Reducing likelihood of deadlocks (was referential Integrity and SHARE locks)
Следующее
От: Gregory Stark
Дата:
Сообщение: Re: Variable length varlena headers redux