Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YlM4R-0002Es-G4 for pgsql-bugs@arkaria.postgresql.org; Thu, 23 Apr 2015 18:41:55 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1YlM4Q-0005Js-Un for pgsql-bugs@arkaria.postgresql.org; Thu, 23 Apr 2015 18:41:54 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1YlM4P-0005I9-Lu for pgsql-bugs@postgresql.org; Thu, 23 Apr 2015 18:41:53 +0000 Received: from mail-wi0-x230.google.com ([2a00:1450:400c:c05::230]) by magus.postgresql.org with esmtps (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1YlM4M-0001NA-9o for pgsql-bugs@postgresql.org; Thu, 23 Apr 2015 18:41:52 +0000 Received: by wicmx19 with SMTP id mx19so18845407wic.1 for ; Thu, 23 Apr 2015 11:41:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=iBiSlK8/GuOLC+U4LEZcz7Ubnd5cu9sWP6mr/B7ZrvU=; b=eGqlIQElCunaqBPvIjWJiJr8sNrMV1jJNVYlbVwGQss+NRz5B87ODNdJecVMD5Epwz 74yXf5L7qZHR34kKp9J9WS7rfDhVij9ZM2LusH4EPYrx8qHwTZybP4D/ErpU/zBofV6s 19NvzvV6escNmAY+fdfRgPrIamIdCrvJRBHFtoD8b8ifdRKWNGuQjr0ZrLCI5Dp2slAF kSyIm5nu2bkzceJ8RSTeXah/AB2x9eMgArROpD34aK7TjDdoawbJMewoYkcAUCvgDlic d8LmN+UtbjGPZQc4mtFtIHvYnn5rQJlFDzjK6U3l8y7WOh4yrtpPme3LT7FIhCWhPKWw J0eA== X-Received: by 10.180.97.129 with SMTP id ea1mr18385923wib.24.1429814509232; Thu, 23 Apr 2015 11:41:49 -0700 (PDT) Received: from [192.168.1.99] (dsl-hkibrasgw1-58c38f-82.dhcp.inet.fi. [88.195.143.82]) by mx.google.com with ESMTPSA id mv11sm22875wic.23.2015.04.23.11.41.46 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 23 Apr 2015 11:41:47 -0700 (PDT) Message-ID: <55393CE9.3040805@iki.fi> Date: Thu, 23 Apr 2015 21:41:45 +0300 From: Heikki Linnakangas Reply-To: hlinnaka@iki.fi User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.6.0 MIME-Version: 1.0 To: Michael Paquier , grant@amazon.com CC: pgsql-bugs@postgresql.org Subject: Re: BUG #13128: Postgres deadlock on startup failure when max_prepared_transactions is not sufficiently high. References: <20150422220940.5216.95902@wrigleys.postgresql.org> <5538A018.9030608@iki.fi> In-Reply-To: <5538A018.9030608@iki.fi> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.4 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-bugs Precedence: bulk Sender: pgsql-bugs-owner@postgresql.org On 04/23/2015 10:32 AM, Heikki Linnakangas wrote: > Attached is a patch for that. I introduced this bug in commit > bb38fb0d43c8d7ff54072bfd8bd63154e536b384, which added the proc-exit hook > and the call PostPrepare_Twophase(), so unless you see more bugs in > this, I'll commit and backpatch this to all versions. Committed. - Heikki -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs