From: Tom Lane <tgl@sss.pgh.pa.us>
To: pavan95 <pavan.postgresdba@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Too many serialization errors in production
Date: Wed, 17 Apr 2019 09:53:42 -0400
Message-ID: <28176.1555509222@sss.pgh.pa.us> (raw)
In-Reply-To: <1555481397393-0.post@n3.nabble.com>
References: <1555481397393-0.post@n3.nabble.com>
pavan95 <pavan.postgresdba@gmail.com> writes:
> We are facing the error "*could not serialize due to concurrent update*" too
> many times in our production server.
Why do you think there are too many? For an app that's depending on
isolation levels above Read Committed, that's an expected behavior.
> My concern here is if I change this isolation level to "Read Committed" will
> this suffice to stop this error occurrence?
You wouldn't see any more of those errors, but almost certainly you'd
have broken the application. Presumably, it's depending on retrying
serialization failures to ensure consistency across concurrent updates.
Without the retries, such cases would likely soon lead to inconsistent
data.
> Could you please suggest me how to stop any user from changing the
> default_transaction_isolation in PostgreSQL?
That's a spectacularly bad idea.
regards, tom lane
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: tgl@sss.pgh.pa.us, pavan.postgresdba@gmail.com
Subject: Re: Too many serialization errors in production
In-Reply-To: <28176.1555509222@sss.pgh.pa.us>
* 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