Re: BUG #17578: undetected (on one side) deadlock with reindex CONCURRENTLY partitioned index vs drop index

Поиск
Список
Период
Сортировка
От Noah Misch
Тема Re: BUG #17578: undetected (on one side) deadlock with reindex CONCURRENTLY partitioned index vs drop index
Дата
Msg-id 20221005104604.GA2255375@rfd.leadboat.com
обсуждение исходный текст
Ответ на BUG #17578: undetected (on one side) deadlock with reindex CONCURRENTLY partitioned index vs drop index  (PG Bug reporting form <noreply@postgresql.org>)
Список pgsql-bugs
Дерево обсуждения 
On Fri, Aug 05, 2022 at 09:16:57PM +0000, PG Bug reporting form wrote:
> My expectations was that the session with longer deadlock timeout should
> always win and session with shorter deadlock timeout should lost locking
> race (and error out with deadlock message).

That holds if all edges of the deadlock are in lock waits by the time of the
shorter deadlock timeout.  Otherwise, since each session runs the deadlock
detector only once, the longer timeout will be the one to error out.

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

Предыдущее
От: Masahiko Sawada
Дата:
Сообщение: Re: BUG #17619: AllocSizeIsValid violation in parallel hash join
Следующее
От: Noah Misch
Дата:
Сообщение: Re: BUG #17616: Silently skipping to update data to the database with owner privileges using flyway scripts