Re: BUG #17578: undetected (on one side) deadlock with reindex CONCURRENTLY partitioned index vs drop index - Mailing list pgsql-bugs

From Noah Misch
Subject Re: BUG #17578: undetected (on one side) deadlock with reindex CONCURRENTLY partitioned index vs drop index
Date
Msg-id 20221005104604.GA2255375@rfd.leadboat.com
Whole thread Raw
In response to BUG #17578: undetected (on one side) deadlock with reindex CONCURRENTLY partitioned index vs drop index  (PG Bug reporting form <noreply@postgresql.org>)
List 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 by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: BUG #17619: AllocSizeIsValid violation in parallel hash join
Next
From: Noah Misch
Date:
Subject: Re: BUG #17616: Silently skipping to update data to the database with owner privileges using flyway scripts