From: Noah Misch <noah@leadboat.com>
To: maxim.boguk@gmail.com
To: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17578: undetected (on one side) deadlock with reindex CONCURRENTLY partitioned index vs drop index
Date: Wed, 5 Oct 2022 03:46:04 -0700
Message-ID: <20221005104604.GA2255375@rfd.leadboat.com> (raw)
In-Reply-To: <17578-6c41993c9876cb92@postgresql.org>
References: <17578-6c41993c9876cb92@postgresql.org>
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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: noah@leadboat.com, maxim.boguk@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17578: undetected (on one side) deadlock with reindex CONCURRENTLY partitioned index vs drop index
In-Reply-To: <20221005104604.GA2255375@rfd.leadboat.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox