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 <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1hIVbG-0008EP-Gq
	for pgsql-admin@arkaria.postgresql.org; Mon, 22 Apr 2019 09:50:58 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.89)
	(envelope-from <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1hIVbE-0001mC-Ux
	for pgsql-admin@arkaria.postgresql.org; Mon, 22 Apr 2019 09:50:56 +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 <pavan.postgresdba@gmail.com>)
	id 1hIVbE-0001m5-M0
	for pgsql-admin@lists.postgresql.org; Mon, 22 Apr 2019 09:50:56 +0000
Received: from n3.nabble.com ([162.255.23.22])
	by magus.postgresql.org with esmtp (Exim 4.89)
	(envelope-from <pavan.postgresdba@gmail.com>)
	id 1hIVbC-0006mg-1W
	for pgsql-admin@postgresql.org; Mon, 22 Apr 2019 09:50:56 +0000
Received: from n3.nabble.com (localhost [127.0.0.1])
	by n3.nabble.com (Postfix) with ESMTP id C16E013765F6C
	for <pgsql-admin@postgresql.org>; Mon, 22 Apr 2019 02:50:51 -0700 (MST)
Date: Mon, 22 Apr 2019 02:50:51 -0700 (MST)
From: pavan95 <pavan.postgresdba@gmail.com>
To: pgsql-admin@postgresql.org
Message-ID: <1555926651747-0.post@n3.nabble.com>
In-Reply-To: <28176.1555509222@sss.pgh.pa.us>
References: <1555481397393-0.post@n3.nabble.com>
 <28176.1555509222@sss.pgh.pa.us>
Subject: Re: Too many serialization errors in production
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
List-Id: <pgsql-admin.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-admin@lists.postgresql.org>
List-Owner: <mailto:pgsql-admin-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-admin>
Precedence: bulk

Hi Tom,

Thank you so much for your timely response. 

So you are suggesting that changing isolation level from the ODOO
application side/ limiting a user to execute "set
default_transaction_isolation='Repeatable Read' is a bad idea correct?

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?

Looking forward to hear from you.

Regards,
Pavanteja.A,
9841380956



--
Sent from: http://www.postgresql-archive.org/PostgreSQL-admin-f2076596.html