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

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Reducing likelihood of deadlocks (was referential Integrity and SHARE locks)
Дата
Msg-id 1124.1171384714@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: Reducing likelihood of deadlocks (was referential Integrity and SHARE locks)  (Marc Munro <marc@bloodnok.com>)
Ответы Re: Reducing likelihood of deadlocks (was referential Integrity and SHARE locks)  (Marc Munro <marc@bloodnok.com>)
Список pgsql-hackers
Дерево обсуждения 
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.
        regards, tom lane

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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: XML changes broke assert-enabled vcbuild
Следующее
От: Marc Munro
Дата:
Сообщение: Re: Reducing likelihood of deadlocks (was referential Integrity and SHARE locks)