Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dJtjU-0004qQ-D1 for pgsql-bugs@arkaria.postgresql.org; Sun, 11 Jun 2017 03:40:08 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dJtjT-00067R-SQ for pgsql-bugs@arkaria.postgresql.org; Sun, 11 Jun 2017 03:40:07 +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_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dJtik-0001Xu-Jy for pgsql-bugs@postgresql.org; Sun, 11 Jun 2017 03:39:22 +0000 Received: from mail-qk0-x232.google.com ([2607:f8b0:400d:c09::232]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1dJtih-0002ku-93 for pgsql-bugs@postgresql.org; Sun, 11 Jun 2017 03:39:22 +0000 Received: by mail-qk0-x232.google.com with SMTP id r62so18264863qkf.0 for ; Sat, 10 Jun 2017 20:39:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=wORHQdVNpP6o7bomQjCsTyUwp/3ZvCWtHzZ1IlkjOe8=; b=DSCwUmI52uq6yJ60xOf4XFIFwCCb/qEczJ/qo5QUunnQVH0aCedGNMBwm5hg5J/j0l LAKypHU8ukki861rMmmI3gkQmpOjwEbzZxkU5x3XhOc9/H+KuQcty/caG1ZYvtk9YqlX 6zPkDsKKRPJNu1mfChML2iDrySu7o4xflfXDFTr0QPXyrhzRC55CNuqJckp87o9lU0uJ /g4E1tX7B6CRgIizfh2HV1cwvhwZX96y0WzC6ZCJvYD9a2xgB0mC4j2k0RQ1Cy2MkmO5 VBIUll9NAMQ21mVvrrLDuWmTLoRBTUBOb79v+sYb1656tZbp2w+mqeNdecggYLbrEoIz 1wow== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=wORHQdVNpP6o7bomQjCsTyUwp/3ZvCWtHzZ1IlkjOe8=; b=e0oB4amkxlZ0JVs3mDWZN1MvIFVLzAvJ3gp4p0plBfsoKMxaN2MndC+U28rqcCywUh 8cEFLWMoPZD7CyXzVL8vb/P6cra2xBDFiD8on96f3utPyty2xU79kRz+GoL4Ql3WyNKa yPxORcJduXqg6Fgm9vnNPCj+n80wgNdUFd2oc4xqb0FKRHd70kJZrGIcLYupJqhAQTx5 NvtMhmQAL5U9/FkhR5KAEVWKzhVyL7Z+rjFjyr8lBr4sCTgBpHe6LKBFteRgh3WjiTbh C+ERq5SysbpE2MD7BbCFFakqT9QDXxtFQTvG91WDcHq1KoxssR/OQ1ku9kfOuxqqgXZu xASA== X-Gm-Message-State: AKS2vOy5h5ZXzGzrdz1EQF3ewKes0uFx9erpg2ML6NpIfKxWYxLtADnU s/AzqO9l5V53qDjB+7E2OQ== X-Received: by 10.55.45.198 with SMTP id t189mr58368292qkh.108.1497152357626; Sat, 10 Jun 2017 20:39:17 -0700 (PDT) Received: from alvin.alvh.no-ip.org ([186.9.128.128]) by smtp.gmail.com with ESMTPSA id a62sm3891076qkd.14.2017.06.10.20.39.16 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 10 Jun 2017 20:39:17 -0700 (PDT) Received: by alvin.alvh.no-ip.org (Postfix, from userid 1000) id CB89723E2; Sun, 11 Jun 2017 00:28:48 -0300 (-03) Date: Sat, 10 Jun 2017 23:28:48 -0400 From: Alvaro Herrera To: wangchuanting Cc: pgsql-bugs@postgresql.org Subject: Re: Re: BUG #14680: startup process on standby encounter a deadlock of TwoPhaseStateLock when redo 2PC xlog Message-ID: <20170611032848.xazvtrdyhruoxonq@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1496301068099-5964241.post@n3.nabble.com> User-Agent: NeoMutt/20170306-137-4415bd-dirty (1.8.0) 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 wangchuanting wrote: > we use Postgres-XC+pg10(4 coordinator + 4 datanode(pg 10 as datanode, and 1 > master 1 standby for each datanode)), and benchmark tpcc, there is some > cross datanode transactions that use 2pc, during testing, we restart the > cluster, then one datanode standby can not recovery done and hangup with > TwoPhaseStateLock deadlock. > > and sorry, we reinstall the cluster, and the log is removed, we will try to > reproduce, but anyway, the code is not right like Michael saied. Did you have any luck reproducing the original issue? It would be good if you could confirm that the bug is gone with the patch I posted in https://www.postgresql.org/message-id/20170611022536.goef4cdbmgicye5g@alvherre.pgsql Thanks -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs