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 1hJiTO-0005sL-KQ for pgsql-admin@arkaria.postgresql.org; Thu, 25 Apr 2019 17:47:51 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hJiTN-0001G4-B0 for pgsql-admin@arkaria.postgresql.org; Thu, 25 Apr 2019 17:47:49 +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 1hJiTM-0001BF-SV for pgsql-admin@lists.postgresql.org; Thu, 25 Apr 2019 17:47:49 +0000 Received: from mail-qt1-x844.google.com ([2607:f8b0:4864:20::844]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hJiTJ-00064t-RP for pgsql-admin@postgresql.org; Thu, 25 Apr 2019 17:47:48 +0000 Received: by mail-qt1-x844.google.com with SMTP id h16so1070619qtk.6 for ; Thu, 25 Apr 2019 10:47:45 -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=B0ZoAUsLgHVV71SdNhLsGtQ+DgmrPnlz52iigZhRCV0=; b=CQRmpMvC2BSIHmJMXObZTsHmvONpLPAOMTz3ZUbAasq7+YZFadh7Ic+JDLQEDdo7HE 2YvaAn/ioneRWqmaiVsJIlRJPyo7jsHSGSeOAMxz7Chr2Y+/Rka57/fb03mtvimoS2OD 02FFWM1Ca1ttlteWcXjr+ysVPFD3lCkKFEGapm0Ai9l4yC+STuNM2tVpGiAPuiSk2yrq L2HHVRrE0OkKUh64mxmC6xyVN2jAgMo1E5pFPMdNwP5qtLntruL3rUwEfSLXj2hxR7cV iN6e6As4R3zllTizmunhCbPT/IgrdIGXFzN8mc7phOu4f7tw+P2PvCsKSzYpZD8TtExV VqxA== 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=B0ZoAUsLgHVV71SdNhLsGtQ+DgmrPnlz52iigZhRCV0=; b=Q1qot1h47PY7ekEzKPi0ZrNZ+ULbypdGbfzzt3oGtBSdUeJjHx0y/vCwooLurvFsjI xtojKx0vYTLesoVW+3NqMRT5vJToPFvN8J1NDYItIp9t8dVnFBMtr6X08rZDMfOP1D87 gczaSu4InorZi/JzmmK5aKHgcrG+oUudA4fFYOoKDgM6HqIE3nbPZ8MuvnejLNwI9A9A 5dgrs88AUqC7TX6vyMTUHNamDWWpPDD2VFmGaZ5fkaDj/5QqQtI+9h6oYDQdC+C936pz d1k2ynQPeUYgm4+Cy4zUNPWUNS342ITL4jE1el3C707I2wRqdxmtMVkFSDw9++2Q0B2x gfnQ== X-Gm-Message-State: APjAAAXM6nP7KtOS+VYp8KpPK+R+yIdK7Un61xDm00wog2sYKuS2Gq1g 0XLFGubnVmBWc4wzhxyw7XLzaA== X-Google-Smtp-Source: APXvYqyXe3X3lLfJDygN1lCmRJQL/bvVQWAFkz35tA4ZrJfRe26AN5dzrUOsHLp9NdvXODxTsdWhGg== X-Received: by 2002:aed:20c4:: with SMTP id 62mr30595028qtb.256.1556214462963; Thu, 25 Apr 2019 10:47:42 -0700 (PDT) Received: from nimloth.alvh.no-ip.org ([190.121.29.3]) by smtp.gmail.com with ESMTPSA id p27sm13777922qte.25.2019.04.25.10.47.41 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 25 Apr 2019 10:47:42 -0700 (PDT) Received: by nimloth.alvh.no-ip.org (Postfix, from userid 1000) id AA6031208F5; Thu, 25 Apr 2019 13:47:38 -0400 (-04) Date: Thu, 25 Apr 2019 13:47:38 -0400 From: Alvaro Herrera To: pavan95 Cc: pgsql-admin@postgresql.org Subject: Re: Too many serialization errors in production Message-ID: <20190425174738.GA31344@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1555939076842-0.post@n3.nabble.com> User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hello On 2019-Apr-22, pavan95 wrote: > Do you mean this to be a bug? A bug fixed two years ago, yeah. > My question is in my error log I'm getting query text for that corresponding > "could not serialize access due to concurrent update" error failures. But > can I get the other transaction which committed and which is responsible for > this above serialization update? You probably *can*, by ensuring that all transactions have sufficient details in the log; you may be able to link the entries by PID or XID. Not sure how easy that is. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services