Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1og1uq-0003bt-79 for pgsql-bugs@arkaria.postgresql.org; Wed, 05 Oct 2022 10:46:16 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1og1uo-0005cy-5C for pgsql-bugs@arkaria.postgresql.org; Wed, 05 Oct 2022 10:46:14 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1og1un-0005bZ-Ls for pgsql-bugs@lists.postgresql.org; Wed, 05 Oct 2022 10:46:13 +0000 Received: from mail-oa1-x32.google.com ([2001:4860:4864:20::32]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1og1uj-0003zA-R2 for pgsql-bugs@lists.postgresql.org; Wed, 05 Oct 2022 10:46:13 +0000 Received: by mail-oa1-x32.google.com with SMTP id 586e51a60fabf-1322fa1cf6fso12174673fac.6 for ; Wed, 05 Oct 2022 03:46:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leadboat.com; s=google; h=user-agent:in-reply-to:content-disposition:mime-version:references :message-id:subject:to:from:date:from:to:cc:subject:date:message-id :reply-to; bh=H+MJ6DbMKRPaQ5lyrY0tdDydQj83XZf1UGWrPLqSHKc=; b=DMYp3Zlh3bKZEkRKTwfJ7UOzm3Ib0zoJP+6s2fs4RwJqy+YJf/AU0HwSkGfMyZEWJt uKFqJELqsLpWXY6A4YVFRHeHKvFnLsfFInSIMQJfBDJCV4dLL8uXfgrCUI6J/G/D/3dq BuoPoQzTEym0jHkFPUGQ2D7+vbF52DUvRDleA= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=user-agent:in-reply-to:content-disposition:mime-version:references :message-id:subject:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=H+MJ6DbMKRPaQ5lyrY0tdDydQj83XZf1UGWrPLqSHKc=; b=ZFdy0NVMnRCaIDVWcJcmNaismbDzbrCRBfey+OVmthb9p0lJeLIBrgzdpYRoGxX8Cv gP2Ku4V5RwkJ7fjyccAWnSwpxZ9kDlvHPcT3LRr/8K1EU/1dqdQfZKo+Vaq2+kAZM3av brzbMgIt4qsUj0TsG/j9QqPOE4qnIBdVgtWcxfgzksTDxnJppt1DroHc78ZCi2btjxgJ 09wqi8hRPCIahOaPCXG5WuzQ7AmpmDOeZUj4xnbKabNLfUDfrYjs+UteQx1/KazpGcOP ClgsGWVVrtQCxSRQ/2AX9F12s80TkaPF80VCs6u/Yoeksnb5wXEJW+loQSlsS1vn5Cc/ +f7Q== X-Gm-Message-State: ACrzQf0RDsLLAj6koaAWGVtTTXvMNr2ppfViYYC71kFgXY+5tTYtQS7I dzHOLIuziV60f9rfco+kngxURw== X-Google-Smtp-Source: AMsMyM6sdSuVCGgrFqQ88dIgPeEUd6yr1ZnPwsOz66KtQI87C0jQGGO3BrRC1i8zAI3bYFX6uexx7g== X-Received: by 2002:a05:6870:898e:b0:12b:3e64:e86d with SMTP id f14-20020a056870898e00b0012b3e64e86dmr2202525oaq.265.1664966767717; Wed, 05 Oct 2022 03:46:07 -0700 (PDT) Received: from rfd.leadboat.com ([2600:1702:a20:5750::2e]) by smtp.gmail.com with ESMTPSA id l41-20020a4a94ec000000b0044b125e5dabsm3134795ooi.35.2022.10.05.03.46.06 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 05 Oct 2022 03:46:07 -0700 (PDT) Date: Wed, 5 Oct 2022 03:46:04 -0700 From: Noah Misch To: 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 Message-ID: <20221005104604.GA2255375@rfd.leadboat.com> References: <17578-6c41993c9876cb92@postgresql.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <17578-6c41993c9876cb92@postgresql.org> User-Agent: Mutt/1.5.24 (2015-08-30) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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.