From: pavan95 <pavan.postgresdba@gmail.com>
To: pgsql-admin@postgresql.org
Subject: Re: Too many serialization errors in production
Date: Mon, 22 Apr 2019 02:50:51 -0700 (MST)
Message-ID: <1555926651747-0.post@n3.nabble.com> (raw)
In-Reply-To: <28176.1555509222@sss.pgh.pa.us>
References: <1555481397393-0.post@n3.nabble.com>
<28176.1555509222@sss.pgh.pa.us>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: pavan.postgresdba@gmail.com
Subject: Re: Too many serialization errors in production
In-Reply-To: <1555926651747-0.post@n3.nabble.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox