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

From: Noah Misch <noah(at)leadboat(dot)com>
To: maxim(dot)boguk(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17578: undetected (on one side) deadlock with reindex CONCURRENTLY partitioned index vs drop index
Date: 2022-10-05 10:46:04
Message-ID: 20221005104604.GA2255375@rfd.leadboat.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Noah Misch 2022-10-05 11:02:09 Re: BUG #17616: Silently skipping to update data to the database with owner privileges using flyway scripts
Previous Message Masahiko Sawada 2022-10-05 04:56:38 Re: BUG #17619: AllocSizeIsValid violation in parallel hash join