Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.500.231\))
Subject: Re: ERROR: could not serialize access due to concurrent update
From: Scott Ribe <scott_ribe@elevated-dev.com>
In-Reply-To: 
 <CAKDb7aFLkz2btDpnkmefDBa-N=kUJ9HYhPmmD1o5+sLqYewY6A@mail.gmail.com>
Date: Tue, 16 May 2023 12:08:45 -0600
Cc: Laurenz Albe <laurenz.albe@cybertec.at>,
 pgsql-admin@lists.postgresql.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <474BDC88-BFEA-4D62-9D43-E0E7ABA1A13A@elevated-dev.com>
References: 
 <CAKDb7aFR1B7wvaLBxBDdark7jx=y31BY74WKdrPF1Zq5xwT+mA@mail.gmail.com>
 <CAKDb7aHL=NXzcFyL5oM3V6=D9P4VVdx_Gd=FskdbeqCotKFSSg@mail.gmail.com>
 <580a59b7e6ef605000c5dde862300e4290d9445a.camel@cybertec.at>
 <CAKDb7aGaZ94nxr1gSw2NfLu5arec9G+SOBDGRV7njxG_C5TZeg@mail.gmail.com>
 <6d2162718b0af8504c5f85013b78dc97a2046d59.camel@cybertec.at>
 <CAKDb7aFLkz2btDpnkmefDBa-N=kUJ9HYhPmmD1o5+sLqYewY6A@mail.gmail.com>
To: ROHIT SACHDEVA <sachdeva.rohit648@gmail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/474BDC88-BFEA-4D62-9D43-E0E7ABA1A13A%40elevated-dev.com>
Precedence: bulk

> On May 16, 2023, at 11:24 AM, ROHIT SACHDEVA =
<sachdeva.rohit648@gmail.com> wrote:
>=20
> But due to this error our transaction is aborted and application team =
are getting these errors in their logs.
>=20
> How can I figure this out?=20
> Can there be work around for not getting this error.

As suggested previously, repeat the query.

It would be good, of course, to reduce the frequency of the errors by =
figuring out what is conflicting--are the queries generally taking too =
long compared to their frequency? But repeating a query when a lock =
conflict blocks it would still be the ultimate fallback, and is pretty =
standard practice.