Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hsJP4-0003gS-HG for pgsql-hackers@arkaria.postgresql.org; Tue, 30 Jul 2019 04:06:22 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hsJP3-0006Sl-DJ for pgsql-hackers@arkaria.postgresql.org; Tue, 30 Jul 2019 04:06:21 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hsJP3-0006Sd-4w for pgsql-hackers@lists.postgresql.org; Tue, 30 Jul 2019 04:06:21 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hsJP0-0008EH-Sq for pgsql-hackers@postgresql.org; Tue, 30 Jul 2019 04:06:20 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id x6U46242019330; Tue, 30 Jul 2019 00:06:02 -0400 From: Tom Lane To: Alvaro Herrera cc: Robert Haas , Michael Paquier , Andres Freund , PostgreSQL Hackers Subject: Re: TopoSort() fix In-reply-to: <20190730032157.GA652@alvherre.pgsql> References: <20190730032157.GA652@alvherre.pgsql> Comments: In-reply-to Alvaro Herrera message dated "Mon, 29 Jul 2019 23:21:57 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <19328.1564459562.1@sss.pgh.pa.us> Date: Tue, 30 Jul 2019 00:06:02 -0400 Message-ID: <19329.1564459562@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Alvaro Herrera writes: > On 2019-Jul-29, Tom Lane wrote: >> FYI, I just got done inventing a way to reach that code, and I have >> to suspect that it's impossible to do so in production, because under >> ordinary circumstances no parallel worker will take any exclusive lock >> that isn't already held by its leader. > Hmm, okay, so this wasn't a bug that would have bit anyone in practice, > yeah? That's reassuring. At the least, you'd have to go well out of your way to make it happen. regards, tom lane